Turn collector YAML into
managed rollouts.
Store, version, assign, and roll out collector configs from one place. Compare intended state with the effective config each collector actually reports, and roll back instantly when anything looks wrong.
Every config is a versioned object.
Push from the UI, the CLI, or a Git commit — every save is a new immutable version with a SHA, an author, a message, and a diff.
- Immutable version history, indexed by SHA
- Inline YAML editor with schema-aware validation
- Compare any two versions, side by side
Catch the gap between
intended and effective.
OpAMP gives you the config a collector reports it's actually running. We diff that against what you asked for — and surface every mismatch.
- Per-collector intended vs effective comparison
- Filter the inventory to only drifted collectors
- One-click reapply or quarantine
Assign configs by label, not by hostname.
Group collectors with labels — environment, region, role — and bind a managed config to a label expression. New collectors that match the label inherit the config automatically.
- Label-based selectors with full Boolean operators
- Preview the matched set before you assign
- Per-config and per-collector pin overrides
Undo a bad rollout in one click.
Every prior version is one button away. Roll back to a known-good config across the entire fleet, or scope the rollback to a single label set.
- One-click revert to any prior version
- Scoped rollback for partial recoveries
- Auto-rollback on health threshold breach (Business+)
From YAML to running collector,
in four steps.
Author
Edit YAML in the UI, push from CLI, or commit to Git.
Validate
Schema check, processor compatibility, and dry-run before save.
Roll out
Stage to a label slice, watch live progress, fan out when green.
Reconcile
Effective config reports back. Drift surfaces immediately.
Ready to manage configs the way you ship code?
Start free, connect a collector in monitor-only mode, and turn on managed mode whenever you're ready.