Health monitoring¶
Health Monitor is the read-only operational inventory for devices, applications, cloud services, and integrations that report health to TEKControl. Use it to identify missing heartbeats, degraded components, unhealthy dependencies, and the last known state before opening a support case or changing a related configuration.
Open General Administration and select Health Monitor. This action requires Site Admin-level authority or higher.
Note
Health Monitor shows reported technical health. It does not prove that every business workflow is functioning, and it does not replace the alert-management controls under Health Notifications.
Understand the scope¶
The available clients and sites follow your administrative assignments:
- platform administrators can monitor all clients and sites;
- client-wide administrators can monitor sites belonging to their assigned clients;
- site administrators can monitor only their assigned sites.
Cloud-service targets are visible only to platform administrators. The other target types are AllBox, access controller, camera, integrated device, integration service, desktop app, and other.
Interpret status and heartbeat¶
The displayed status is an effective status. TEKControl first evaluates the target heartbeat:
- If no heartbeat exists, the target is Offline.
- If the last heartbeat is older than the target's offline threshold, the target is Offline.
- Otherwise, TEKControl displays the target's reported overall status.
The default offline threshold is 180 seconds when the target has no specific threshold. A target can therefore appear Offline even when its last reported status was Healthy.
| Status | Meaning |
|---|---|
| Healthy | The heartbeat is current and the target reports no degraded or unhealthy condition. |
| Degraded | The target is reporting but at least one condition is impaired. |
| Unhealthy | The target is reporting a serious health failure. |
| Offline | The heartbeat is missing or older than the allowed threshold. |
| Unknown | The target is reporting a state that cannot currently be classified as healthy. |
Offline and Unhealthy appear as critical badges; Degraded and Unknown appear as warning badges. Treat the color as a triage aid, not as a substitute for reviewing component details.
Filter the inventory¶
Use Client, Site, Target Type, Status, and search to narrow the grid. Search matches the target key, display name, device identifier, source application, and summary.
Two operational filters are especially useful:
- Problems only includes stale or offline targets plus targets reporting Degraded, Unhealthy, or Unknown.
- Stale reports only includes only targets with a missing or late heartbeat.
These filters are not equivalent. A currently reporting target can be unhealthy without being stale, while a previously healthy target can become offline because it stopped reporting.
The grid displays at most 1,000 matching targets. Narrow the client, site, type, or search when the expected target does not appear.
Read the grid¶
The inventory shows the client, site, post, target, type, effective status, reporting source, device identifier, last report, last seen online, and summary.
Dates are displayed in the site's configured time zone when one is available; otherwise they are displayed in UTC. Last Seen Online normally uses the current heartbeat while the target is online. For an offline target, TEKControl uses the stored lastOnlineUtc or lastConnectedUtc metadata when available. A blank value means no usable online timestamp was reported.
Investigate a target¶
Select the eye action or double-click a row to open the target details. Review its identity before drawing conclusions, especially when names or device identifiers are similar. Then inspect:
- Components and events for the affected subsystem and status history;
- the source application's logs or field diagnostics;
- the related TEKControl configuration, network path, credentials, and external provider;
- Health Notifications to determine whether an alert exists and who has acknowledged it.
Health Monitor does not modify, restart, acknowledge, suppress, or resolve a target. Correct the underlying device or service condition through its approved operational process.