The System Health screen shows the versions of the components installed on your server, the host server's current resource usage, the status of the data-processing pipelines, and the state of every node in the deployment.
Installed Components
1. Lists the version identifiers of every software component running on this deployment. Quote these when reporting an issue to Teramind support.
Field | Description |
UI version | The version of the web interface package installed on the server. |
API version | The version of the Teramind API the server exposes. |
Server | The server build number. |
TMU version | The Teramind Update (TMU) package version currently installed. This is the primary indicator of your deployment version. |
Schema version | The version of the database schema. |
Windows agent version | The Windows Agent installation package hosted by this server for new installations and updates. |
Windows ARM agent | The Windows ARM Agent installation package hosted by this server. |
MacOS agent version | The macOS Agent installation package hosted by this server. |
Linux agent version | The Linux Agent installation package hosted by this server. |
The Agent versions listed here are the packages the server offers for download; the Agent versions card shows the versions Agents are actually running.
System Load
2. Displays the host server's current resource usage.
Field | Description |
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. |
BI Status
3. Shows the status of the business intelligence sync (used for data displayed on the dashboards) and categorization engine.
Field | Description |
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 field displays Not available if no categorizer package is installed. Check out [this article] on the Knowledge Base 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. |
Sync Progress | Appears during an active sync, showing the percentage complete. It is hidden when the sync is idle. |
Session Mining Stats
4. Shows the health of the session mining pipeline, which processes captured screen recordings into searchable data. This card appears only when OCR is enabled on the instance; it is hidden when OCR is off.
Field | Description |
Last mined piece of data | The timestamp of the most recent screen data processed by the OCR mining pipeline. A timestamp that stops advancing indicates session mining has stalled. |
OCR delay | The current mining delay: the backlog between screen content being recorded and its OCR processing completing. A small delay is normal; a consistently growing delay indicates mining capacity is falling behind the recording volume. |
Nodes:
5. Lists every node registered in the deployment, with its current state. A single-node deployment shows only the Master row; multi-node deployments also list their worker nodes.
Column | Description |
Role | The node's function in the cluster, for example Master, Screen mining database node, Screen mining node, or IMS (a node running the optional Omni analytics services, present only on deployments where Omni is enabled). |
Ip Address | The node's network address as registered with the master. |
State | A green Alive badge means the node is responding; a red Unreachable badge means the master cannot reach it and the node should be investigated. |
Disk | Disk space used versus total capacity on the node's volume. Shows Not available when the node does not report volume statistics (for example, while it is unreachable). |
Agent Versions
6. Lists each Agent version currently reporting to this deployment and the number of computers running it, ordered by count. Only computers that connected within the last 31 days are counted; the card header states the exact number of computers included. Use this card to confirm an Agent rollout is progressing: several versions listed side by side is common during a rollout period, while a long tail of old versions indicates computers that have not yet updated.
7. Click Refresh stats at the top-right of the screen to reload the latest figures.