Vision and ambition
FleetAMP aims to become an open, vendor-neutral management plane for telemetry collectors and related agents. Telemetry backends answer questions about applications and infrastructure; FleetAMP focuses on the operational system that creates, governs and runs the telemetry pipeline itself.
Product ambition
FleetAMP is intended to connect five concerns that are commonly fragmented:
- Fleet operations — inventory, identity, health, versions and lifecycle.
- Configuration delivery — versioned desired state, validation, targeting, deployment status and rollback.
- Governance — ownership, approval separation, policy, drift and audit.
- Enablement — guided instrumentation, reusable blueprints and destination profiles for common telemetry patterns.
- Intelligence — explainable signals about telemetry quality, volume, cardinality, cost, sensitive data and operational drift.
The goal is not to replace OpenTelemetry, a telemetry backend, Git, an identity provider or a CMDB. FleetAMP should integrate with those systems through clear boundaries while retaining a small, understandable core.
Community edition
The community project is self-hosted and Apache-2.0 licensed. Development is public, contributions are welcome and roadmap pages distinguish implemented capabilities from exploration. Pre-1.0 releases are intended for evaluation and controlled pilots while compatibility, recovery and scale expectations mature.
Success criteria
FleetAMP succeeds when a platform team can explain, for every managed Collector: who owns it, what it should run, what it actually runs, who requested and approved a change, what happened during deployment and how the platform recovered from failure.