Skip to main content

Put Nova on call

NovaNova
How do I route my alerts to Nova?
Ask Nova

Rather not read it all? Ask Nova this. It walks you through each step.

By the time someone is paged, the cause is found, the fix waits for approval, and the postmortem is drafted.

Who does what: Sam (SRE, org admin) routes the alerts and owns the postmortem. Alice (platform engineer, org owner) chooses who approves. Dana (on-call engineer, org admin) answers the page and approves the fix. Bob (developer, org editor) owns pods-probe-web, which starts crash-looping.

You need the AstroPulse skill connected (Set up Nova for your team, step 1), and alerting on your apps.

1. Sam routes the alerts​

In Nova > Settings > Incidents, select Create alert token and copy the Alertmanager receiver into Alertmanager (Alerts).

Open zoom view

Nova Settings, Incidents: Alerts from Alertmanager or Grafana, Create alert token, and Post results to Slack channel

Nova Settings, Incidents: Alerts from Alertmanager or Grafana, Create alert token, and Post results to Slack channelNova Settings, Incidents: Alerts from Alertmanager or Grafana, Create alert token, and Post results to Slack channel

2. Alice chooses who approves​

In Nova > Settings > Guardrails > Who approves, set Who may approve a change to Owners and admins only.

3. Dana reads the cause and approves the fix​

When the investigation opens, Dana opens it in Nova > Investigations, reads the cause, and on Redeploy pods-probe-web with the nginx-unprivileged image selects Let Nova fix it.

Open zoom view

A resolved investigation: the cause that the container runs as a non-root user and cannot write to a path nginx needs, the quoted nginx chown error from the app logs, the fix marked Fix applied, and the health check showing pods-probe-web recovered

A resolved investigation: the cause that the container runs as a non-root user and cannot write to a path nginx needs, the quoted nginx chown error from the app logs, the fix marked Fix applied, and the health check showing pods-probe-web recoveredA resolved investigation: the cause that the container runs as a non-root user and cannot write to a path nginx needs, the quoted nginx chown error from the app logs, the fix marked Fix applied, and the health check showing pods-probe-web recovered

4. Sam reads the postmortem​

Open the full record > Postmortem shows each step, its time and who took it (what the postmortem holds).

Open zoom view

The postmortem timeline from Investigation started to Nova applied the approved fix and verified pods-probe-web's health, then the primary root cause

The postmortem timeline from Investigation started to Nova applied the approved fix and verified pods-probe-web's health, then the primary root causeThe postmortem timeline from Investigation started to Nova applied the approved fix and verified pods-probe-web's health, then the primary root cause
NovaNova
What was the cause of the pods-probe-web incident?
Ask Nova

Nova answers from the incident's record.

Next​

Nova fixes a crash-looping deploy, the same incident step by step.