Incidentary – see what caused your incident before the war room starts

Show HN: An OTel exporter that posts the cause to your incident channel

Based, Incidentary – see what caused your incident before the war room starts works in show hn launch.

Profile

Hi HN, Ahmed here. If you already run an OpenTelemetry collector, this is the entire install: exporters: otlp/incidentary: endpoint: api.incidentary.com:4317 headers: authorization: "Bearer ${INCIDENTARY_API_KEY}" service: pipelines: traces: exporters: [otlp/incidentary] What it does: when an alert fires (PagerDuty, OpsGenie, a Slack command, or a direct webhook), it takes the trace data your services already emitted in the window around the alert and assembles a causal chain like "service-A's HTTP call to service-B returned 503 at 14:22:03; service-B was timing out on Redis; Redis primary was failing over." That artifact lands in the incident channel before the war room fills up.I built thi

The company sits in the show hn launch segment, where it competes on its core product or service.

Its current recorded stage is Show HN launch.

Website: incidentary.com