---
title: "Self-monitoring | Grafana Labs"
description: "Understanding how Fleet Management monitors your collectors"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Self-monitoring pipelines

Self-monitoring pipelines are configuration that Fleet Management automatically assigns to each registered collector, instructing it to collect and report its own health data, such as CPU usage, memory consumption, component health, and internal logs.

[Self-monitoring: observability for your observability](fleet-management-self-monitoring.svg "Self-monitoring: observability for your observability")

## Why self-monitoring matters

Without self-monitoring, you’d have a blind spot with no visibility into whether your collectors themselves are healthy.

| Scenario                     | Without self-monitoring                     | With self-monitoring                      |
|------------------------------|---------------------------------------------|-------------------------------------------|
| Collector runs out of memory | You don’t know until metrics stop arriving. | You see memory usage climbing.            |
| A component fails            | Silent failure, missing data.               | Component dashboard shows it’s unhealthy. |
| Collector is overloaded      | Data arrives late or not at all.            | Throughput metrics show the issue.        |

> You don’t have to configure this. It’s automatic. Self-monitoring is observability for your observability.