Evidence-first incident analysis

Post-mortems built from the data your database already collected

Gather before, during, and after evidence from metrics, logs, wait events, locks, queries, vacuum activity, and system signals. Optional manual AI can add root cause, timeline, and remediation depth.

When something breaks at 02:14, you don't need another dashboard. You need to know what changed, what it affected, what to do now, and what to tell the team tomorrow.

Multi-window evidence gathering

Error logs, locks, sessions, wait events, query stats, vacuum activity, and system metrics are pulled per time window — not from a single blurry snapshot.

Optional AI root cause analysis

When you choose to run AI analysis, a unified report identifies probable root causes, orders the timeline of events, and explains what caused what in plain language you can share with your team.

Compare before, during, after

Separate data frames for the period before the incident, during, and after recovery — so you can see exactly what changed and when.

Blast radius & impact

See which connections, queries, and tables were affected, how long, and by how much — not just "something went wrong at 02:14".

Concrete remediation steps

Every incident report ends with an ordered list of actions to take now, and longer-term fixes — with the SQL or config change where one exists.

Evidence deep-linking

Every claim in the report links directly to the specific metric, lock chain, or log entry that supports it. No handwaving.

Full incident history

Every analysis is versioned and stored. Build a library of post-mortems and spot recurring patterns across weeks or months.

PDF & HTML export

Export any incident report as PDF or HTML to attach to Jira tickets, share with customers, or circulate to leadership after an outage.

From alert to post-mortem

Start an analysis from a triggered alert, a known time window, or a specific connection — MyDBA does the rest.

How it works

  1. 1Pick a time window — from an alert, an outage report, or a free-form range. MyDBA splits it into before / during / after frames automatically.
  2. 2Evidence is gathered per frame — error logs, locks, sessions, wait events, top queries, vacuum activity, and system metrics are pulled separately for each period so changes are obvious.
  3. 3You choose whether to add AI depth — optional AI can produce root cause, timeline, impact, and remediation, with every claim grounded in the gathered evidence.
  4. 4Review, export, and archive — download as PDF or HTML, or keep the full history in-app to spot recurring patterns.

Related capabilities

See it in action

Start free with one primary or standalone PostgreSQL instance and all its databases. Monitoring, alerts, query insights, index advice, team access and every non-AI feature included. No replicas. No credit card required. New Free connections get seven days of full collection, then reduced sampling. Free and Pro include 30 days of monitoring history.