Agent Details¶
Clicking on any agent card in the Agent Summary opens the Agent Details dialog, which provides a comprehensive view of the agent's runtime information, configuration, and real-time performance metrics.
Alternatively, you can achieve the same goal by clicking on the details icon within the individual agent card's action toolbar.
🪪 Agent Identification¶
The top section of the dialog displays the core identifying information for the agent:
| Field | Description |
|---|---|
| Agent ID | The unique internal identifier assigned to this agent by BizMetry. |
| Agent Name | The human-readable name identifying the agent. |
| Status | The current operational state of the agent (e.g., ONLINE, OFFLINE, RESTARTING). |
| Reachability | Indicates whether the BizMetry platform can currently reach the agent endpoint. An agent may be ONLINE but temporarily Unreachable if network connectivity is interrupted. |
| Profile | The name of the telemetry profile this agent belongs to. |
| Environment | The name and type of the environment this agent is associated with (e.g., my-uat-env · UAT). |
🖥️ Runtime Information¶
When the agent is ONLINE, the following runtime details are available, reflecting the actual execution context of the agent process:
| Field | Description |
|---|---|
| Operating System | The operating system on which the agent is running (e.g., Linux, Windows Server 2022). |
| Architecture | The processor architecture of the host machine (e.g., amd64, arm64). |
| Uptime | The amount of time the agent has been continuously running since its last startup (e.g., 4h 32m). Resets to zero each time the agent is restarted. |
| Last Sync | Timestamp of the last successful synchronization between the agent and the BizMetry platform. During synchronization, the agent exchanges logs, metrics, and configuration updates. |
| Metrics Processed | The total number of business metrics captured and processed by the agent since its last startup. |
| Service Account | The service account configured for authenticating the agent with the BizMetry platform. |
| Log Level | The current logging verbosity level configured for the agent (e.g., INFO, DEBUG, WARN, ERROR). Higher verbosity levels are useful for troubleshooting but may impact performance. |
🌐 Gateway Configuration¶
Agents communicate with both the BizMetry platform and the customer's internal applications through two independently configured gateways:
External Gateway¶
| Field | Description |
|---|---|
| URL | The connection endpoint for the external gateway. |
| Status | Whether the external gateway is reachable and operational. |
The external gateway is used by the BizMetry platform to reach the agent from outside the customer's network. This is typically the URL of an external load balancer or reverse proxy exposed to the internet.
⚠️ If the external gateway is not configured or unreachable, BizMetry will not be able to communicate with the agent, push configuration updates, or retrieve collected data.
Internal Gateway¶
| Field | Description |
|---|---|
| URL | The connection endpoint for the internal gateway. |
| Status | Whether the internal gateway is reachable and operational. |
The internal gateway is used by business applications running within the customer's network to reach the agent and submit metrics — either via auto-instrumentation or the BizMetry SDK. This is typically the URL of an internal load balancer or service endpoint.
⚠️ If the internal gateway is not configured, business applications will not be able to deliver metrics to the agent, regardless of the agent's operational status.
📊 Real-Time Performance Metrics¶
The details dialog displays live resource usage metrics for the agent process, automatically refreshed at regular intervals to ensure the information remains current:
| Metric | Description |
|---|---|
| CPU Usage | Average CPU consumption of the agent process as a percentage of available processing capacity. |
| Memory Usage | Average memory consumed by the agent process as a percentage of available system memory. |
| Latency | Average network round-trip time between the agent and the BizMetry platform, measured in milliseconds. |
⏱️ Performance metrics are refreshed periodically in the background. The timestamp of the last update is displayed alongside the metrics.
🚨 SLA Breaches¶
The SLA Breaches section appears in the Agent Details dialog when one or more SLA thresholds configured for the agent are currently being exceeded. If all SLAs are within their defined limits, this section is not shown.
Each active breach is displayed as an individual entry containing the following information:
| Field | Description |
|---|---|
| Resource | The metric that triggered the breach: CPU, Memory, or Network Latency. |
| Detected At | The timestamp at which BizMetry detected the breach condition for this resource. |
How breaches are detected and resolved¶
BizMetry evaluates SLA conditions periodically for each agent. A breach is triggered when a resource metric remains above the configured SET threshold for longer than the configured Set Time window. The breach entry appears in this section as soon as the condition is confirmed.
A breach is automatically resolved — and its entry removed from this section — when the metric drops below the CLEAR threshold and remains there for the duration of the configured Reset Time window. No manual action is required.
💡 The use of separate SET and CLEAR thresholds, combined with time windows, implements a hysteresis mechanism that avoids false positives and prevents alert flapping caused by transient resource spikes.
⚙️ SLA thresholds and time windows are configured per agent in the Agent Configuration dialog — SLAs tab.
🧭 Summary¶
The Agent Details dialog provides:
- Full identification of the agent including its unique ID, associated profile and environment.
- Runtime context including operating system, architecture, and last synchronization timestamp.
- Operational configuration including service account, log level, and metrics processed count.
- Gateway status for both the external (platform-facing) and internal (application-facing) endpoints.
- Live performance data including CPU, memory, and network latency, refreshed automatically.
- Active SLA breach alerts for any resource currently exceeding its configured thresholds.