Webhooks
Webhooks allow you to integrate the MAR platform with external systems by receiving notifications when events occur.
Overview
The Webhooks page manages webhook endpoints that receive event notifications from the MAR platform.
Webhook Properties
| Property | Description |
|---|---|
| Name | Descriptive name for the webhook |
| URL | Endpoint URL that receives notifications |
| Events | Event types that trigger notifications |
| Status | Current state (active, paused, degraded) |
| Success Rate | Percentage of successful deliveries |
| Total Delivered | Number of successful deliveries |
| Total Failed | Number of failed deliveries |
| Last Delivery | Time of most recent delivery |
Webhook Statuses
- Active - Webhook is receiving event notifications
- Paused - Webhook is not receiving notifications
- Degraded - Webhook has delivery issues
Event Types
Configure which events trigger webhook notifications:
| Event | Description |
|---|---|
| instance.crash | Instance has crashed |
| cluster.degraded | Cluster has become degraded |
| alert.triggered | An alert has been triggered |
| alert.resolved | An alert has been resolved |
| instance.started | Instance has started |
| instance.stopped | Instance has stopped |
| cluster.created | New cluster created |
| * | All events |
Creating Webhooks
- Click the Add Webhook button
- Enter a descriptive name
- Specify the endpoint URL
- Select event types to subscribe to
- Optionally provide a signing secret
- Click “Create Webhook”
Managing Webhooks
Viewing Details
Click on any webhook to see:
- Full configuration
- Delivery statistics
- Signing secret
- Recent delivery attempts
Testing Webhooks
Click the Play button to send a test payload to the webhook endpoint.
Toggling Status
- Pause - Stop delivering events (active webhooks)
- Activate - Resume delivering events (paused webhooks)
Delivery Statistics
Expand any webhook to see:
- Total delivered count
- Total failed count
- Recent delivery attempts with:
- Timestamp
- Status (success/failed)
- HTTP status code
- Duration
- Payload size
Signing Secrets
Webhooks use signing secrets to verify that requests originated from the MAR platform:
- Each webhook has a unique signing secret
- The secret is included in request headers
- Use the secret to verify payload authenticity
- Secrets can be auto-generated or provided manually
Integration Examples
PagerDuty
Send alerts to PagerDuty for incident management.
Slack
Post notifications to Slack channels for team awareness.
Custom HTTP
Send events to any HTTP endpoint for custom processing.
DataDog
Forward events to monitoring systems.
Best Practices
- Use descriptive webhook names
- Monitor delivery success rates
- Set up alerts for webhook failures
- Rotate signing secrets periodically
- Test webhooks after configuration changes
- Use pause status for maintenance windows
Last updated on