Bring GitOps discipline
to OpenTelemetry Collector.
Connect GitHub, watch config paths in your repo, and link every rollout to a commit. Review the diff, roll out to selected collectors, and see exactly which ones applied the change.
Your YAML lives in Git.
So does its history.
Connect a GitHub App once. Tell us which repo, which branch, and which paths. Every commit that touches a watched path becomes a candidate rollout.
- GitHub App with read-only repo scope
- Watch any number of YAML paths or globs
- Branch protection rules carry through to rollouts
Every rollout points back
to a commit.
The diff in O11yFleet is the diff in GitHub. Click the SHA to land on the exact PR that introduced the change, and link rollouts back from your commit history.
- Diff parity with GitHub's own UI
- Bidirectional links between commits and rollouts
- Commit status checks for in-progress rollouts
Codeowners and approvals,
at the rollout boundary.
Reuse your CODEOWNERS file. Require N approvals before a config can be rolled out to a labeled environment. Policy lives next to the YAML, not in a separate UI.
- Reuse CODEOWNERS per path
- Per-environment approval thresholds
- Approval bypass with audited break-glass
Four steps from commit
to running collector.
Connect
Install the GitHub App and pick the repo, branch, and watched paths.
Commit
Push YAML in PRs the way you always have. Branch protection still applies.
Roll out
Approve, target a label, and watch live progress per collector.
Audit
Every rollout is timestamped, signed, and traceable to its commit.
Make Git the only place
collector config changes.
Connect a repo in five minutes. Keep your existing review process. Get a fleet that does what the commits say.