Fleet Management
NoteThis is a private preview feature. Please contact your Observe representative for more information or open Docs & Support → Contact Support in the product and let us know.
What is Fleet Management?
Fleet Management gives you a single place to understand the deployment and health of Observe Agents across your entire environment—Linux, Windows, MacOS and Kubernetes clusters. It is designed to help Observe users quickly diagnose common problems and gather the right information before contacting Support.
Problems Fleet Management helps to solve
Fleet Management can help you answer the following common questions:
Is the Observe Agent healthy?
The Fleet Management surfaces the following metrics:
- Auth check status
- Endpoint connectivity
- Data flow health (logs, metrics, traces)
- Configuration issues
- Version drift
- Workload readiness (Kubernetes)
If something is wrong, Fleet Management shows the symptom and the next likely cause.
If the Observe Agent is not healthy what’s the next thing I should look at?
Fleet Management guides users through a structured troubleshooting workflow:
- Authentication Errors (401 / 403)
- Endpoint Errors (400 / 404 / 500)
- Data Flow Errors (logs, metrics, traces)
- Configuration Issues (multiline, recombine, etc.)
Prerequisites
Fleet Management requires Observe Agent version 2.10.1 or higher. Use the following command to verify your Observe Agent version:
If you haven't installed the Observe Agent, you can do so from the Add Data portal:
- In the left navigation, select Data & integrations > Add data.
- In the Observe Agent section, select your environment, then follow the on-screen instructions to create a token and install the Observe Agent.
Setup
Follow the instructions for your environment to complete the setup.
Enable fleet configuration
Edit your agent configuration:sudo vim /etc/observe-agent/observe-agent.yamlAdd or update:
self_monitoring:
enabled: true
fleet:
enabled: true
interval: 10m
config_interval: 24hRestart the Observe Agent
Run the following command to restart the Observe Agent:sudo systemctl restart observe-agentVerify in Fleet Explorer
Navigate to Data & Integrations > Fleet and confirm your Observe Agent instances appear.
Access Fleet Management
To access the Fleet dashboard, select Data & integrations > Fleet from the left navigation rail. The Fleet dashboard shows you a summary of how many agents you have, their overall health, and provides filters so you can find specific agents by ID, environment, and host.
Click on any agent to view details for that agent, including host logs and metrics, such as CPU and memory usage and other details.
Click on the Observe Agent Config tab to view the observe-agent.yaml configuration for that specific Observe Agent:
Click on the Opentelemetry Collector Config to view the complete OTel configuration being used for this specific Observe Agent.

Updated 8 days ago