Agent Diagnostics

Agent Diagnostics focuses on operational visibility for the Breeze agent process itself. Instead of only checking endpoint health metrics, teams can inspect what the agent is doing internally and why a workflow is failing.

What It Covers

The diagnostics stream includes structured log entries with timestamp, severity level, component, message, and contextual fields. Common components include heartbeat, websocket, main startup flow, and updater lifecycle.

This makes it easier to identify issues such as:

• repeated reconnect loops
• delayed heartbeat cycles
• update failures
• command execution errors
• local environment constraints

Log Shipping and Retention

Agent diagnostic logs are shipped in compressed batches on a regular cadence and can be queried through the API with filters for time range, level, component, and search terms.

By default, logs are retained for seven days. Retention can be extended through environment configuration when longer troubleshooting windows are needed.

Service-Level Troubleshooting

Alongside log visibility, Breeze documents service-management workflows for the agent, especially in Windows environments where service registration and lifecycle controls matter most during deployment and recovery.

Why Teams Use It

Agent Diagnostics shortens mean time to resolution by giving operators direct evidence of transport, scheduling, and execution issues without requiring manual, ad-hoc log collection on each affected endpoint.