Skip to content
BleemeoBleemeo

Agent Dashboard

Free
Starter
Professional

On this page you can see a list of your agents.

For each agent you can see whether it is currently online, the server name, the values of the main metrics, and the list of services with their status indicated by color.

Agent list in Bleemeo showing online status, server name, key metrics, and service health

If you click on the server name, you access the agent page, organized in tabs.

Bleemeo agent dashboard with CPU, memory, IO, and disk gauges and usage charts

The tabs of a server running the Bleemeo agent are, in order:

Tab Content
Dashboard The agent’s dashboard, shown above. When several dashboards are attached to the agent, for instance service dashboards, each one gets a tab named after it. The + button next to them adds one of the available dashboards.
Containers The containers running on the server, see Docker. Only shown when a container runtime is detected.
Processes The live process list, see Processes.
Information An overview of the agent and the server, see Information.
Metrics Every metric collected for the agent, see Metrics.
Health Metric status, health checks and anomalies, see Health.
Events The events raised for this agent.

Other agent types (network devices, cloud resources…) have no Containers or Processes tab, and an AWS account has no Information tab.

While an anomaly is in progress on one of the agent’s metrics, a chip next to the tabs shows how many are live and opens the Anomalies view of the Health tab.

The Information tab gives an overview of the agent:

  • A header with the connection state (how long the agent has been up, or when it was last seen and why it disconnected), and key figures: number of metrics and services, CPU cores and memory. A warning is shown when the agent should be updated.
  • A health at a glance row with the metric status counts, the health check summary and the pending updates. Each of them opens the matching view of the Health tab. Network devices show the connected and disconnected interfaces instead.
  • The Services detected on the server, colored by status, then the agent’s Tags, Dashboards and Applications.
  • The System details, the agent facts grouped by category.

The Metrics tab lists every metric collected for the agent. A rail on the side lists the metric categories (CPU, Disk, Memory, Network, one per service…): click one to show only its metrics. The selected category is kept in the URL, so you can reload the page or share the link. Searching flattens the list across categories, and each result shows its category.

Each row shows the latest value of the metric, a sparkline of the last hour and its thresholds. The row menu can Open in Metrics explorer (see Metrics Explorer) or Copy PromQL selector.

Click a row to open the metric drawer, with a chart of the metric, its status history and its thresholds. From the drawer you can edit the thresholds of the metric. Metrics of cloud resources are collected read-only, so their thresholds can’t be edited.

The Health tab gathers the health signals of the agent. A switch at the top selects the view:

  • Metric status: the metrics having a status, filtered by severity.
  • Health checks: the checks run on the agent, see agent’s health checks.
  • Anomalies: the anomalies detected on the agent’s watched metrics over the last 30 days, see Anomalies.

The selected view is kept in the URL (?section=healthcheck or ?section=anomalies), which is how the Information tab and the anomaly chip link to it.

Beyond the agent’s own dashboard, Bleemeo proposes a dashboard for each service. Each supported service has a layout of its own, and it is offered once two things are true: Glouton has detected the service, and is actually sending at least one of the metrics the layout graphs.

That second condition is why a service can be detected and visible in the services list without its dashboard appearing. It usually means the metrics are missing: the service page’s Metrics are Missing section is the place to start, or Troubleshoot a Service Check or Missing Metrics.

Most services have a dashboard of their own, see Services Monitoring for what each of them collects. If your service doesn’t have one, you can request it from us or build it yourself.