Extend
Integrations
Bridge from docs to production evidence sources — OpenTelemetry, Kubernetes, GitHub, Prometheus, and the marketing Integrations hub.
Docs v1.0Updated Supported
When should I use this?
- You want the evidence-first overview before wiring telemetry in docs.
- You already run Prometheus, Grafana, or Jaeger and need a coexistence story.
- You are evaluating which production evidence sources AutoObserve supports today.
Steps
- Start on the production evidence sources hub — organized by evidence type, not vendor category.
- Connect telemetry via OpenTelemetry, Prometheus, or Jaeger (preview).
- Add runtime and change context with Kubernetes, GitHub, and Argo CD (preview) when available.
- Add cloud and storage context with AWS (preview) or ClickHouse (preview) when needed.
- Return to docs to connect OpenTelemetry, deploy on Kubernetes, or connect metrics.
- Keep existing dashboards and alerting; use AutoObserve for evidence-backed investigations.
What's next?
Continue
Connect OpenTelemetry
Wire OTLP from your collector and verify telemetry in production.
Related
- Production evidence sources
- OpenTelemetry integration
- Kubernetes integration
- GitHub integration
- Prometheus integration
- Jaeger integration (preview)
- Argo CD integration (preview)
- AWS integration (preview)
- Azure integration (preview)
- Google Cloud integration (preview)
- ClickHouse integration (preview)
- Connect OpenTelemetry
- Connect metrics
- API
- Architecture