Used by
OpenAna + Prometheus
Metrics collection, monitoring and alerting with flexible querying.
Live connectionObservability
Ana + Prometheus
What Ana does with it.
Metrics, logs and traces Ana correlates to find root cause and verify every fix.
- 01
Queries metrics during investigations
- 02
Uses utilization history for safe rightsizing
- 03
Proposes alert rule improvements
Setup
Connected in four steps.
- 1
Connect
Open Integrations in Ana and connect Prometheus 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 Prometheus in investigations, fixes and reports, and every action is logged.
In practice
Playbooks that use Prometheus.
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 →SRE / DevOps
Rightsizing cloud spend without breaking SLOs
The cloud bill keeps climbing and nobody is sure which resources are safe to shrink. Ana finds idle and oversized resources, checks them against real utilization and SLOs, and ships the changes as reviewed IaC.
Read the playbook →Governed
Every action, approved and logged.
Ana’s guardrails decide what it may do with Prometheus, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.
FAQ
OpenAna and Prometheus.
No. Ana works with Prometheus - it uses the tool as a source of context and a place to act - so you keep the tool you already run.
Observability
Also in this category.
See it connected
Ana on your Prometheus.
Thirty minutes, your real setup, one real problem.