Check background processes
Identify missing scheduler runs and waiting tasks before troubleshooting each individual workflow.
Module · SuiteUltimateUnderstand what is running.
Understand what is running.
See what needs attention.
Make SuiteCRM system conditions visible: schedulers, storage, database and delivery, with clear findings and next steps.
Health CenterIllustrative example
Overall conditionReview required
49 %A critical core check caps the overall score.
SchedulerReview
File permissionsOK
DatabaseOK
EnvironmentOK
Example data · Not a live measurement of your installation
✓ Five health dimensions✓ Findings with action guidance✓ Database & storage overview✓ Configurable alerts
Clarity in operationsSmall deviations.
Small deviations.
A big impact on daily work.
A missed scheduler run or an unwritable folder can affect several CRM processes at once.
Narrow down the cause
File permissions, runtime configuration and log findings help explain why uploads, delivery or automation are not working as expected.
Assign work effectively
Findings indicate whether CRM administrators, the hosting team or the mail provider should act. Timestamps and evidence make handover easier.
Four perspectives on your operationsDiagnostics that lead
Diagnostics that lead
to a decision.
Technical signals become understandable tasks.
Watch the system heartbeat
Check execution and freshness of background tasks. A missing signal appears as a distinct finding.
Understand growth
Distinguish data and index sizes by module and investigate large tables.
Check prerequisites
Compare write permissions, ownership and runtime settings with the installation's requirements.
Receive relevant signals
Report persistent problems, limit repeated notifications and send an all-clear when a finding is resolved.
Five health dimensionsThe overall picture.
The overall picture.
With findings you can explain.
The health score summarises check results. Critical core checks can cap it; the cause remains directly traceable.
Performance
Database responses, runtime configuration and relevant performance indicators.
Security
File permissions, ownership and potential web exposure of sensitive paths.
Storage
Free capacity, file collections and data and index sizes.
Reliability
Schedulers, background processing and freshness of check results.
Environment
PHP versions, extensions, limits and timezone configuration.
Results include the measurement time, checks performed and areas that could not be checked. A high score is not a security certificate. Storage usage is shown separately: a large table alone is not an error condition.
From a finding to the next actionMore than a warning.
More than a warning.
A traceable investigation task.
Each finding combines severity, measurement evidence, ownership and action guidance. Commands and paths must fit the installation.
| Check area | Typical subject | Responsibility |
|---|---|---|
| Scheduler & Cron | Last execution and expected interval | CRM administration / Hosting |
| Log findings | Error volume and sanitised examples | CRM administration / Development |
| File system | Write permissions, ownership and available capacity | Hosting / Infrastructure |
| Database | Response times, table and index sizes | Database administration |
| PHP & Runtime | Versions, extensions, limits and CLI/web differences | Hosting / Infrastructure |
| Email configuration | Connections and delivery prerequisites | CRM administration / Mail provider |
Repair guidance does not automatically authorise changes. Changes to permissions, configuration or data should be reviewed before execution and tested afterwards.
Environment & permissions
Get the foundations right.
Make configuration differences visible instead of starting from scratch with every symptom.
Write permissions & ownership
Check relevant cache, upload, log and extension directories. Ownership and effective write access are assessed in the context of the executing processes.
PHP environment
Compare web and CLI runtimes, memory and upload limits, session paths and required extensions.
Time & configuration
Expose differing timezone settings and review their impact on scheduled tasks and date handling.
Database & storage
Know where the space goes.
A sorted bar overview makes storage allocation understandable. Measurements and estimates are labelled accordingly.
Illustrative storage allocation
Storage by module
Data and indexes · Arbitrary example values
DataIndexes
From the overview to the table.
Start with the total CRM database size, the storage used by SuiteUltimate tables and their percentage share. The module overview separates data and indexes; the table list adds estimated row counts and sizes.
Shared tables are counted only once. Growth is derived from saved measurements; without comparison data, no trend is shown.
Alerts without the floodReport persistent problems.
Report persistent problems.
Make recovery visible.
Rules determine when, to whom and how often a finding is reported.
Threshold & duration
Use severity and persistence as triggers. Brief deviations can be handled differently from lasting errors.
Throttling & recovery
Repeat intervals and delivery limits constrain notifications. When a check returns to normal, an all-clear can follow.
Add an independent view
If the CRM, scheduler or email delivery fails, internal alerts may fail too. An independently operated heartbeat or availability monitor complements the checks.
Part of your operating proceduresCheck. Prioritise.
Check. Prioritise.
Resolve. Verify.
Quick routine checks and deeper analyses are scheduled to suit the environment.
Start a check
Run routine checks or define an appropriate schedule. Plan deeper analysis with workload and data volume in mind.
Assign findings
Assess critical findings first. Use evidence and ownership information to organise the response.
Apply changes under control
Adapt guidance to the installation. Sanitised JSON or CSV reports support handover to the responsible teams.
Verify the result
Measure again and compare the current state. Reports document the check time; they do not replace a comprehensive operational review.
Frequently asked questions
What you should know.
Answers about diagnostics, analysis and integration into operations.
Do the checks slow down the CRM?
Every check uses resources. Routine checks and deeper analyses are planned separately; data volume, intervals and available capacity determine the workload.
Does the Health Center replace external monitoring?
No. It adds CRM-specific findings. An independent monitor can detect outages during which the CRM itself can no longer run checks or send messages.
How accurate are database sizes and row counts?
Accuracy depends on the database and available statistics. Estimates are labelled. Growth requires multiple saved measurements.
Can reports be exported?
Structured JSON and CSV reports support technical handover and documentation. An export does not itself demonstrate certification.
What information do findings contain?
The focus is technical metadata and measurements. Log excerpts and diagnostic reports must be sanitised and access-controlled; review them before external sharing.
Are problems repaired automatically?
This page describes diagnostics and specific guidance. Changes to files, permissions and configuration remain controlled administrative actions.
What does the health score mean?
It summarises completed checks. Critical core checks may cap the overall score. Individual findings and measurement time are essential to interpreting it.
Modules working togetherDelivery and storage
Delivery and storage
in one operating concept.
Explore the areas relevant to your installation.
See Health Center
in your SuiteCRM?
In about 20 minutes we clarify operational questions and show diagnostics and next steps in SuiteCRM 8.
Request a Health Center demo ↗No obligation · Insights into diagnostics & alerts