Webhooks with NeuBird, the AI SRE: any alert, investigated
NeuBird accepts custom events and alerts through its Event Ingestion API, so a signal from any system, including your own, can start an investigation.
< 5 min
Root cause, at 94% accuracy
15+
Sources queried in parallel per investigation
In place
No bulk telemetry stored
< 1 hour
To deploy on the stack you already run
Core Capabilities
From signals to solutions
Resolve
Any alert can start an investigation
When your system posts an event with the investigate flag set, NeuBird opens an investigation in the project the webhook belongs to, reads the event’s title, payload and labels, and queries the project’s other connections in parallel. The root cause comes back with the evidence attached.
- Uses the event’s title, labels and payload as the starting point
- Routes each event to the project its webhook connection belongs to
- Root cause in under 5 minutes at 94% accuracy, posted where your team works
Prevent
Signals from in-house systems count too
NeuBird takes events from homegrown monitors, batch jobs and scripts that no dedicated connection covers, so early warnings from those systems reach the same investigation as the rest of your telemetry.
- Brings custom health checks and job failures into NeuBird
- Lets each event set whether it starts an investigation
- Correlates custom events with changes across your stack
Operate
One intake for every alert source
NeuBird gives every system the same intake: one endpoint, an ingest token per webhook connection and optional HMAC signing to verify each request.
- Verifies request bodies with an HMAC secret in the X-Hub-Signature-256 header
- Keeps a separate ingest token for each webhook connection
- Remembers every verified fix, with no bulk telemetry stored
Better Together
Webhooks + NeuBird
| Capability | Webhooks and Event Ingestion | NeuBird |
|---|---|---|
| Delivers events from any system | ✓ | Accepts them through the Event Ingestion API |
| Request signing | ✓ | Verifies HMAC signatures |
| Correlation with telemetry, cloud and code changes | Not in scope | 15+ sources in parallel |
| Root cause with cited evidence | Not in scope | Under 5 minutes, 94% accuracy |
| Staged fix or rollback | Not in scope | Behind configurable human approval gates |
| Memory of past fixes | Not in scope | Verified fixes, no bulk telemetry stored |
Ecosystem
Works across your entire stack
Webhooks and Event Ingestion is one piece of the picture. NeuBird queries it in place and correlates it with every other connected tool, and every agent in the center inherits the connection.
Observability
- Prometheus
- Grafana
- Datadog
Incident management
- PagerDuty
- ServiceNow
- Opsgenie
Collaboration
- Slack
- Microsoft Teams
Code and change
- GitHub
- GitLab
FAQ
Common questions
How do I send events to NeuBird?
You create a Webhook connection in NeuBird, optionally with an HMAC secret, copy the ingest token it shows once, and add the connection to a project. Your system then posts events to the Event Ingestion API with the token in the Authorization header.
What does an event contain?
An event has an ID, a title, a creation time, an investigate flag and a payload. The payload can carry the source, severity, message and labels such as environment and service.
How are webhook requests verified?
Every request carries the ingest token as a bearer token. If you set an HMAC secret on the connection, each request also carries a SHA-256 signature of the raw body in the X-Hub-Signature-256 header.
When should I use a webhook instead of a dedicated connection?
Use a webhook for systems with no dedicated NeuBird connection, such as in-house monitors, batch jobs or scripts. For tools among NeuBird’s 50+ integrations, use the dedicated connection so NeuBird can query the tool directly.
Get Started
Connect Webhooks and Event Ingestion to the center.
Webhooks and Event Ingestion gives you the data. Connect it to NeuBird once, and every agent that touches production inherits it, including the ones you build yourself.
