Introduction
The System Health page provides a real-time overview of your Teramind deployment's infrastructure status - including server resources, service containers, database health, and agent versions. Use it to quickly verify that the deployment is operating normally or to diagnose performance issues.
System Load:
1. Displays the host server's current resource usage.
Total Number of Cores | The number of CPU cores available to the server. |
5 Minutes Load Average | The average CPU load over the last 5 minutes, displayed as a percentage. A consistently high value may indicate the server is under heavy processing load. |
Memory Usage | RAM currently in use versus total available, with the utilization percentage. High usage is expected on smaller deployments; sustained pressure on production servers warrants investigation. |
Storage | Local disk space used versus total capacity. Monitor this to ensure adequate space for recordings and logs. |
Remote Storage (S3) | Indicates whether remote S3 storage is enabled for offloading recordings and exports. Shows Enabled or Disabled. |
Server Time | The current date and time on the server. Useful for confirming time synchronization across your environment. |
TMU Version | The Teramind Update (TMU) package version currently installed. This is the primary indicator of your deployment version. |
BI Status:
2. Shows the status of the business intelligence sync (used for data displayed on the dashboards) and categorization engine.
Categorizer Version | The version of the BI categorization/classification engine (TeraCat). The categorizer is responsible for classifying app/web domains into categories like “Computer & Internet”, “IT Bulletin Boards”, “Native App”, etc. It also populates data dimensions/columns like Reputation and Security Category in dashboards like Applications & Websites.
The filed displays Not available if no categorizer package is installed. Check out this article on to learn how you can update your BI classifications/categorization engine. |
Categorization | Whether the categorization engine is Enabled or Disabled. |
Last Sync | The timestamp of the most recent BI data sync. A stale timestamp may indicate a sync issue. A Sync Progress indicator appears during an active sync, showing the percentage complete. It is hidden when the sync is idle. |
Agent Versions:
3. Displays the range of agent versions currently reporting to this deployment, broken down by platform.
Windows | The version (or min–max range if multiple builds are in use) of Windows agents. Shows Not available if no Windows agents are reporting. |
Mac | The version (or min–max range) of Mac Agents. Shows Not available if no Mac Agents are reporting. |
Linux | The version (or min–max range) of Linux Agents. Shows Not available if no Mac Agents are reporting. |
If a range is shown (e.g., 25.41.2961 – 26.24.4149), it means different monitored computers are running different Agent versions, which is common during a rollout period.
Containers:
4. Lists all Docker containers powering the deployment, with their current status. The header shows the timestamp of the last refresh.
Container | The Docker Compose container/service na,e (e.g., v2-server-1, teraweb, clickhouse). |
Runtime State | How long the container has been running, e.g., “Up 7 days”, |
Health | Green Healthy or red Unhealthy badge. All containers should be Healthy under normal operation. |
Build No. | The image/build number (when available). Some infrastructure containers may not display a build number. |
Key containers and their roles:
| NextGen application components: API, UI, WebSocket, and reverse proxy. |
| NextGen background sync pipeline. |
| NextGen exports and mail notifications managers. |
| NextGen deployment orchestration and log forwarding. |
| Legacy web, engine, WMI stack. |
| Legacy BI/analytics pipeline. |
Databases
5. Shows the health and version of each database used by the deployment.
PostgreSQL | Engine version, approximate data size, and health status. This is the primary relational database. |
Redis | In-memory data store version, size, and health. Used for caching and real-time operations. |
ClickHouse | Legacy columnar analytics database version, size, and health. |
Next-Gen Database | The NextGen database identifier (typically Default on single-tenant installations). |
Next-Gen Schema | The NextGen schema identifier, typically shown as “v2”. |
Session Mining Stats (OCR) - Conditional
6. This section only appears if OCR session mining is enabled on your instance. It shows:
Last Mined Piece of Data | Timestamp of the most recently OCR-processed data. |
OCR Delay | Current mining delay/backlog indicator. |