Health target components and events¶
Open a row from Health Monitor to inspect a target's reported identity, component state, and recent health events. This dialog is read-only.
Confirm the target identity¶
The summary identifies the client, site, post, target type, managed entity, source application, serial number, version, environment, operating system, architecture, runtime, device identifier, and target key when those values have been reported.
Also review:
- Last Report: most recent target heartbeat received by TEKControl;
- Last Seen Online: most recent usable online or connected timestamp;
- Last Status Change: time the target's overall status last changed;
- Report Interval: how frequently the target expects to report;
- Offline After: how late a heartbeat may be before the target is considered Offline;
- Summary: target-provided explanation of its current overall condition.
Dates use the site's configured time zone when available and UTC otherwise. Missing values mean the reporting source did not provide them; they are not proof that a feature is disabled.
Components¶
The Components tab shows the latest reported state for each subsystem within the selected target. Filter by status or search the component name, key, type, message, and error details.
| Column | Interpretation |
|---|---|
| Component | Reported component name or key. |
| Type | Category such as database, camera, process, listener, dependency, or storage. |
| Status | Component's current reported health state. |
| Observed | Time this component state was observed. |
| Latency | Reported response or processing delay, when measured. |
| Error | Reported error code or condensed failure detail. |
| Message | Human-readable condition reported by the source. |
Select a component to display its raw details in Selected Details. This JSON may include provider responses, endpoint names, paths, exception information, or implementation-specific fields. Use it for diagnosis, but do not paste credentials, tokens, personal data, or sensitive infrastructure details into an unrestricted ticket or chat.
A healthy overall target can still contain a recently changed or informational component. Conversely, an unhealthy target can have many healthy components and one failing dependency. Focus on the component that explains the overall summary and observed time.
Events¶
The Events tab lists the newest registration and status-change events, up to 500 entries. Filter by event type or search the summary and event details.
| Column | Interpretation |
|---|---|
| Event Time | When TEKControl recorded the event, in the site time zone or UTC fallback. |
| Type | Registration or status-change event. |
| Old / New | Status transition reported for a status-change event. |
| Summary | Condensed event explanation. |
Select an event to display its raw payload in Selected Details. Events are a recent operational trail, not a complete audit archive. Repeated Healthy-to-Offline transitions often indicate an unstable connection, overly aggressive offline threshold, overloaded reporting source, or intermittent dependency.
Investigation workflow¶
- Confirm the client, site, post, source, and device identifier.
- Compare Last Report with the configured reporting interval and offline threshold.
- Find the first unhealthy or degraded component and note its observed time, latency, message, and error.
- Review Events for the transition into the current state and any repeated recovery cycle.
- Correlate the timestamps with deployment, maintenance, network, provider, or configuration activity.
- Correct the underlying system and verify that a new heartbeat and healthy component state arrive.
If the monitor and the physical device disagree, do not manually reinterpret the badge. Confirm UTC versus site time, target identity, source reporting, and connectivity using Troubleshooting.