New Feature: Recovery notifications are now available for webhook, Slack, and email destinations! Get notified when your alerts return to normal state.
Alert destinations determine where notifications are sent when alerts are triggered or resolved. Metoro supports multiple destination types, allowing you to route alerts to the right teams and systems.

Supported Destination Types

Slack

Send alert notifications directly to Slack channels for immediate team visibility.Key Features:
  • Direct channel integration
  • Rich message formatting
  • Alert status and details
  • Recovery notifications support
  • Deep links to Metoro

PagerDuty

Integrate with PagerDuty for on-call management and incident response.Key Features:
  • Automatic incident creation
  • Service-level routing
  • Escalation policy support
  • Auto-resolution on recovery

Email

Send alert notifications via email to specific recipients.Key Features:
  • Multiple recipients
  • Detailed alert information
  • HTML-formatted messages
  • Recovery notifications support
  • Direct links to details

Webhook

Send alerts to custom endpoints for integration with any system.Key Features:
  • Custom HTTP POST requests
  • JSON payloads
  • Trigger & recovery support
  • Configurable endpoints

Guardian AI

Automatically trigger Guardian AI to investigate alerts.Key Features:
  • Automated root cause analysis
  • Alert correlation
  • Remediation suggestions
  • Workflow integration

Configuring Alert Destinations

1

Navigate to Alert Configuration

Open your alerts page in the Metoro, then select the alert you want to configure destinations for, or create a new alert.
2

Add Destination

In the “Select Destination” section, click the Add Destination button
3

Choose Destination Type

Select your preferred destination type from the dropdown menu
4

Configure Settings

Enter the destination-specific settings (channel, email, webhook, etc.)
5

Save Configuration

Save your alert configuration to activate the destination
Alert Destination Selector

Alert destination selector interface

Multiple Destinations

You can configure multiple destinations for a single alert to ensure notifications reach all necessary channels and teams.
  • Click Add Destination for each additional destination
  • Each destination operates independently
  • Mix different destination types as needed
Multiple Destinations

Multiple destinations configured for comprehensive alerting

Recovery Notifications

Recovery notifications are available for webhook, Slack, and email destinations, allowing you to know when alerts return to normal state.

What are Recovery Notifications?

Recovery notifications inform you when an alert condition is no longer met and the alert has returned to a normal state.
Include $alert_uuid and $alert_state variable in your webhook payload to differentiate between firing and resolved states for the same alert.
Include $fire_alert_uuid variable in your webhook payload to differentiate between different firing instances of the same alert. This is useful is you have a group by in your alert configuration because alerts with a group by can have multiple firing instances. For example, if you have an alert that is grouped by with service.name, each service will have its own firing instance with a unique $fire_alert_uuid.

Configuring Recovery Notifications

1

Add a Slack Destination

Select Slack from the destination type dropdown and choose your channel
2

Enable Recovery Notifications

Check the “Notify when alarm recovers” checkbox that appears next to the Slack destination
Slack recovery notifications are sent to the same channel as firing notifications, with clear visual indicators (✅ for resolved vs 🔥 for firing).
Recovery Notification Configuration

Webhook recovery notification configuration showing both firing and resolved webhook options

Recovery Webhook Payload

{
  "alert_state": "resolved",
  "resolved_at": "2024-01-15T10:30:00Z",
  "alert_uuid": "abc-123",
  "alert_name": "High CPU Usage",
  "environment": "production",
  "service": "api-server"
}
The alert_state field is critical for distinguishing between trigger and recovery notifications. Always validate this field in your webhook handler.
Plese see the webhook documentation for more details on how to configure these payloads: Webhook Documentation.

Troubleshooting

You can check webhook delivery status and errors in Metoro Logs view. This provides visibility into successful deliveries and any issues encountered. Go to the Logs page and filter by envrionment=metoro-internal and service.name=metoro-webhooks to see webhook notifications that are successfully sent or failed with errors.

Quick Reference


Need Help?Join our Slack community for support, or contact support@metoro.io for assistance with alert destinations.