Fleet Management¶

synthkit's Fleet Management integration registers fake Alloy collectors with the Grafana Cloud Fleet Management API and emits their full Alloy self-metric set. The result is a realistic collector roster on the Fleet Management page — complete with per-OS breakdowns and component health — with no real Alloy agents running.

What it does¶

At startup, a background controller goroutine owns all FM API side effects:

Register — each fake collector calls RegisterCollector with its deterministic ID, OS type, collector version, and local_attributes (including collector.os and collector.version, which drive the FM UI's "Operating System" and "Alloy version" columns).
Heartbeat — every 45 seconds, each collector calls GetConfig with local_attributes set. FM tracks liveness by heartbeat recency; omitting local_attributes causes collectors to go inactive.
Unregister — on shutdown, collectors are cleanly unregistered.

The emitter reads the controller's roster and pushes Alloy self-metrics to Mimir each tick. Stale-series cleanup ensures that when the roster shrinks (or when collector scaling changes), departed collectors' up=1 series do not persist after unregistration.

Emitted signals¶

For each registered collector, synthkit emits the full Alloy self-metric set against job="integrations/alloy":

Metric	Type	Notes
`alloy_build_info`	Gauge	`version` must start `"v"`
`up`	Gauge	1 = healthy, 0 = unhealthy
`alloy_component_controller_running_components`	Gauge	`health_type` ∈ {`healthy`, `unhealthy`, `unknown`, `exited`}
`alloy_component_evaluation_seconds`	Histogram	24 obs/tick
`alloy_resources_process_cpu_seconds_total`	Counter
`alloy_resources_process_resident_memory_bytes`	Gauge
`alloy_resources_machine_rx_bytes_total`	Counter
`alloy_resources_machine_tx_bytes_total`	Counter
`alloy_config_hash`	Gauge	`hash=sha256hex(collectorID)`
`go_goroutines`	Gauge
`go_memstats_heap_inuse_bytes`	Gauge
`scrape_duration_seconds`	Gauge

Base labels on every series: job="integrations/alloy", namespace="infra", cluster, k8s_cluster_name, instance, collector_id, os.

Intentionally not emitted: remotecfg_*, prometheus_remote_storage_*. These are real-Alloy remote_write internals that would misrepresent a fake collector.

The full signal contract is in signals/fm.md on GitHub.

Credentials¶

FM registration uses its own credential pair — distinct from the Mimir push credentials.

GC_FM_STACK_ID is the Grafana Cloud stack ID, not GC_PROM_USER

The FM API uses HTTP Basic auth with the stack ID as the username. This is a different number from the Mimir instance ID (GC_PROM_USER). Check the Fleet Management page in Grafana Cloud for your stack ID.

Env var	Description
`GC_FM_URL`	FM API URL, e.g. `https://fleet-management-prod-0NN.grafana.net`
`GC_FM_STACK_ID`	FM Basic-auth username = Grafana Cloud stack ID (not `GC_PROM_USER`)
`GC_FM_TOKEN`	CAP token with `fleet-management:write` scope

When the credential triplet is absent, the FM construct emits metrics only — no API registration calls are made.

See Credentials for token-scoping guidance.

Enabling Fleet Management¶

Add a fleet_management block under features: in a blueprint. The construct is substrate-scoped: series are disambiguated by collector_id and carry no blueprint label.

Standalone collector fleet¶

features:
  fleet_management:
    enabled: true
    collectors_per_os:
      linux: 12
      windows: 4
      darwin: 3

Each OS entry produces that many fake collectors with deterministic IDs of the form <blueprint>-<env>-<os>-<NN>. Absent OS types emit nothing.

See blueprints/fleet-management.yaml for a complete reference example, or blueprints/hostfleet.yaml for a combined host-fleet setup.

k8s-monitoring collector mirror¶

When a cluster has k8s_monitoring.fleet_management: true, synthkit additionally registers the Alloy collectors that a real grafana/k8s-monitoring Helm chart deployment (v3) would create — alloy-metrics, alloy-singleton, alloy-logs, alloy-profiles, alloy-receiver — each feature-gated to match the chart's behaviour. See blueprints/synthetic-monitoring.yaml for a combined SM + FM example.

LLM-assisted setup¶

The /setup-fleet-management skill walks through credential configuration, .env setup, and live verification. Run it from Claude Code after opening this repo, or install the synthkit plugin from any compatible agent runtime:

/setup-fleet-management

See Tools for the full skill inventory.

FM page badge¶

The FM online-status badge (green/red) reflects heartbeat recency tracked by a Redis TTL in Grafana Cloud, not metric presence. A firing alert carrying collector_id is required to show a red "unhealthy" badge. Metric-only simulation affects dashboards but not the FM page badge — this is a cosmetic limitation of the fake-collector model.