Skip to main content
Obsy provides a unique per-organization webhook URL for each supported monitoring platform. When an alert fires, the platform POSTs to your URL, and Obsy normalizes it into an Alert entity, runs RCA, and optionally creates an incident.

​
Your webhook URLs

Go to OTel Collector → Create Monitors to see your URLs, or fetch them directly:
Response:

​
Platform setup

Detailed steps: Datadog alerts · Grafana alerts · New Relic alerts

​
What happens when a webhook arrives

  1. Parse — payload is normalized to a common Alert format (service, severity, signal type, labels)
  2. Store — Alert is saved with a link to the raw payload for debugging
  3. RCA — if severity is critical, an AI analysis starts in the background
  4. Auto-incident — if an auto-create rule matches, an incident is created
  5. Slack — if an incident is created and Slack is configured, a channel is opened and notifications are sent

​
Security

Webhook endpoints use your unique organization identifier in the URL path for authentication. This identifier is a random UUID that is not publicly discoverable. For additional security:
  • Datadog: You can configure webhook signing in Datadog’s webhook settings for payload verification.
  • Grafana / New Relic: The unique URL serves as the authentication mechanism.
If your security team requires IP allowlisting or webhook signature verification, contact support@obsy.ai.

​
Generic webhook (custom integrations)

For tools not listed above, use the generic endpoint:
Payload:
The source field accepts: datadog, grafana, prometheus, otel, custom.