Integrations — On-call and alerting
NerveStax and Opsgenie
Alerts are investigated before they become an Opsgenie alert.
What we do
What NerveStax does with Opsgenie
Send your Airflow, dbt and webhook failures to NerveStax instead of straight to your pager. An agent investigates each one with read-only tools, resolves the noise with its reasoning written down, and escalates the rest to Opsgenie with the likely cause and evidence attached. Opsgenie keeps the rotations and the routing rules.
-
Triage before anyone is notified
Alerts reach NerveStax first. The agent reads the failed task's logs, the lineage around it and recent changes, then reaches one of two verdicts: resolved, or escalate.
-
Close noise with a written reason
Self-healed retries, transient infrastructure failures and forty downstream alerts from one upstream break end as resolved, with the full transcript of the investigation kept.
-
Escalate with a diagnosis
A real incident reaches Opsgenie with the likely cause, what depends on the broken asset and the evidence behind that reading, so triage starts before the phone rings.
-
Unsure still escalates
A crash, a timeout, a missing verdict or an inconclusive one all page. Nothing is silently eaten, and an uncertain agent escalates rather than guessing a cause.
-
Recorded before it is sent
Escalations are written to the record first, so an outage at the paging provider delays delivery without losing the incident. The triage stays readable in the product.
Background
About Opsgenie
Opsgenie is an alerting and on-call service: it takes alerts, applies routing and escalation rules, and notifies whoever is on the rota until someone acknowledges.
How it connects
What connecting it looks like
-
01
Create an Opsgenie API integration
Add an API integration on the team that should receive data platform alerts, and copy its API key.
-
02
Add the key in NerveStax
Paste it in as the escalation target for the workspace. It is stored encrypted and no screen shows it back.
-
03
Point your alerts at NerveStax
Use the per-project webhook URL for Airflow failure callbacks, dbt run and test results, or anything else that can POST JSON.
-
04
Review the first week
Read what was resolved and what was escalated, then decide what else to route in. The transcripts show the reasoning for each.
Scope
What this does not cover
- Escalation is one-way: NerveStax raises an alert in Opsgenie. It does not read alert state back, sync acknowledgements, or manage your rotas.
- Triage is read-only. Code fixes still arrive as a tested pull request a person approves.
- Every escalation also lives in NerveStax with its full diagnosis, whether or not delivery succeeds.
Questions
Opsgenie and NerveStax
Q01Do we still need Opsgenie?+
Yes, and that is the point. Opsgenie keeps the rotations, routing rules and notification policies. NerveStax changes what arrives there: alerts that were investigated first, so the ones that reach a person are real and carry a likely cause rather than a task name and a retry count.
Q02How much noise actually gets closed?+
It depends on your platform, so we will not quote a number. What is fixed is the behaviour: an alert is only resolved when the agent can show why, with the reasoning recorded, and anything it cannot prove resolved is escalated instead.
Q03What if triage crashes or times out?+
It escalates anyway. Fail-open is deliberate: crash, timeout, missing verdict or inconclusive all page a human. An alert storm short-circuits to escalation too, rather than spending model budget on forty copies of one failure.
Q04Can the agent change things while triaging?+
No. It holds read-only tools during triage, with no repository or write access while a raw alert payload is in its context, and the payload is fenced as untrusted input rather than treated as instructions. Its only writes are the verdict itself.
Q05What can send alerts into it?+
Anything that can POST JSON. Airflow task and DAG failure callbacks and dbt run and test results are understood natively; everything else arrives through a generic webhook with a per-workspace, revocable token.