OpenAna + OpenTelemetry

Unified distributed tracing and metrics collection.

Live connectionObservability

Ana + OpenTelemetry

What Ana does with it.

Metrics, logs and traces Ana correlates to find root cause and verify every fix.

01
Follows traces across services to the failing hop
02
Adds instrumentation where coverage is missing
03
Uses traces to verify fixes

Setup

Connected in four steps.

1
Connect
Open Integrations in Ana and connect OpenTelemetry with a scoped token, OAuth app or service account.
2
Scope it
Start read-only and choose which projects, repositories or accounts Ana can see.
3
Set the rules
Decide which actions need approval and who approves them - Ana’s guardrails enforce it.
4
Put it to work
Ana uses OpenTelemetry in investigations, fixes and reports, and every action is logged.

In practice

Playbooks that use OpenTelemetry.

SRE / DevOps

From a 3 a.m. page to root cause and fix

An alert pages the on-call engineer. By the time they open the laptop, Ana has correlated metrics, logs, traces and recent deploys, named the likely cause, and drafted the remediation for approval.

Read the playbook →

Used by

Ana’s engineers

SRE / DevOps →Software →

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with OpenTelemetry, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.

Guardrails →Trust center →

FAQ