Overview

Integrations connect Easyalert to your monitoring and observability tools. When an alert fires in your monitoring system, it’s sent to Easyalert via webhook, automatically creating an incident and triggering the appropriate escalation policy.

Automatic Detection

Easyalert automatically detects the source type and extracts relevant fields

Custom Mapping

Map severity levels and enrich alerts with additional context

Real-Time Processing

Alerts are processed instantly and trigger escalations immediately

Sample Analysis

View and analyze incoming webhooks to fine-tune your configuration

Supported Integrations

Easyalert supports the following monitoring tools out of the box:

Zabbix

Open-source enterprise monitoring

Prometheus

Cloud-native monitoring with Alertmanager

Grafana

Unified alerting and legacy alerts

Datadog

Cloud-scale monitoring and security

Dynatrace

AI-powered observability platform

AppDynamics

Business and application performance

New Relic

Full-stack observability platform

Custom Webhook

Any tool that can send HTTP webhooks

How Integrations Work

Create Integration in Easyalert

Add a new integration and select the source type (Zabbix, Prometheus, Grafana, Datadog, or Custom)

Copy Webhook URL

Copy the unique webhook URL generated for this integration

Configure Your Monitoring Tool

Set up your monitoring tool to send alerts to the webhook URL (webhook, notification channel, or media type depending on tool)

Send a Test Event

Trigger a test alert and verify it appears in Easyalert

Configure Routing (Optional)

Set up severity mapping, enrichment, and escalation routing rules

Creating an Integration

Navigate to Integrations

Go to Integrations page from left menu

Click Add Integration

Click the Add Integration button

Select Source Type

Choose the Source Type that matches your monitoring tool (Zabbix, Prometheus, Grafana, Datadog, or Custom)

Enter Details

Name — Descriptive name (e.g., “Production Prometheus”, “Zabbix DC1”)
Description — Optional explanation

Save and Copy URL

Click Create to save and copy the generated Webhook URL

Each integration gets a unique webhook URL. Keep this URL secure as anyone with access can send alerts to your account.

Webhook URL Structure

Your webhook URL follows this format:

https://api.easyalert.io/api/v1/webhooks/ingest/{token}

Example: https://api.easyalert.io/api/v1/webhooks/ingest/wh_abc123...

The token is a unique identifier for your integration. If compromised, you can regenerate it from the integration settings.

Viewing Integrations

The Integrations page shows all your configured integrations:

Column	Description
Name	Integration name and description
Type	Source type badge (Zabbix, Prometheus, etc.)
Events	Total number of events received
Last Event	When the last event was received
Status	Active or Inactive
Actions	View URL, configure, edit, delete

Integration Statistics

Each integration tracks:

Event Count — Total alerts received
Last Event — Timestamp of most recent alert
Last Error — Most recent processing error (if any)
Consecutive Errors — Count of sequential failures

Managing Integrations

View Webhook URL

Click the three-dot menu (⋮)
Select View Webhook URL
Copy the URL to your clipboard

Regenerate Token

If your webhook URL is compromised:

Click the three-dot menu
Select Regenerate Token
Confirm the action

Regenerating the token invalidates the old URL immediately. Update your monitoring tool configuration with the new URL.

Activate/Deactivate

Toggle integration status without deleting:

Click the three-dot menu
Select Activate or Deactivate

Inactive integrations ignore incoming webhooks.

Delete Integration

Click the three-dot menu
Select Delete
Confirm deletion

Deleting an integration permanently invalidates its webhook URL and removes all configuration.

Configuring Severity Mapping

Map source severity values to Easyalert’s standard levels.

Standard Severity Levels

Level	Description	Color
Critical	Requires immediate attention, service down	Red
High	Serious issue, significant degradation	Orange
Warning	Potential issue, investigate	Yellow
Info	Informational alert, low impact	Blue
OK	Recovery/resolved state	Green

Easyalert automatically maps common severity values from monitoring tools. See individual integration guides for specific mappings.

Setting Up Mappings

Open Configuration

Click three-dot menu → Configure Mappings

Set Source Field

Enter the field name your tool uses for severity (e.g., “priority”, “level”)

Add Mappings

Map each source value to a standard severity: - “P1” → Critical - “P2” → High - “P3” → Warning

Set Default

Choose the fallback severity for unmapped values

Example: Datadog Priority Mapping

{
  "sourceField": "alert_priority",
  "mappings": {
    "P1": "critical",
    "P2": "high",
    "P3": "warning",
    "P4": "info",
    "P5": "info"
  },
  "default": "warning"
}

Configuring Enrichment

Add static metadata to all alerts from an integration.

Use Cases

Add environment tags (production, staging, dev)
Identify the team responsible
Add region or datacenter information
Tag for routing rules

Adding Enrichment

Open Configuration

Click three-dot menu → Configure Mappings → Enrichment tab

Add Key-Value Pairs

Enter the key and value for each enrichment field

Save Changes

Click Save to apply

Example: Production Environment Enrichment

{
  "enrichment": {
    "tags.environment": "production",
    "tags.team": "platform",
    "tags.region": "eu-west-1",
    "tags.tier": "critical"
  }
}

Enrichment fields can be used in escalation routing rules to direct alerts to the appropriate policy.

Tag-Based Routing

All integrations support tag-based routing for escalation policies and notification rules.

How Tags Work

From Source: Tags come from your monitoring tool (Zabbix host tags, Prometheus labels, Datadog tags, etc.)
From Enrichment: Static tags added via integration configuration
From Payload: Custom fields in the webhook payload automatically become tags

Routing Examples

Escalation Routing:

tags.customer equals "AcmeCorp" → Acme Corp Policy
tags.environment equals "production" → Production Policy
tags.team equals "backend" → Backend Team Policy

Notification Rules:

tags.severity equals "critical" → call + sms + email
tags.environment equals "staging" → email only
tags.team equals "database" → Database Team channel

See individual integration guides for specific tag configuration instructions.

Webhook Samples

Easyalert stores samples of incoming webhooks for debugging and configuration.

Viewing Samples

Navigate to Configuration → Webhook Samples
Filter by integration
View raw and transformed payloads

Sample Analysis

The analysis feature helps you understand:

Which fields are present in your alerts
Common values for key fields
How to configure severity mappings

Auto-Detection

Easyalert automatically detects the source type based on payload characteristics:

Source	Detection Signals
Zabbix	`event_id`, `trigger_name`, `trigger_severity`
Prometheus	`alerts` array, `status: firing/resolved`
Grafana	`ruleId`, `orgId`, `dashboardURL`
Datadog	`alert_id`, `datadoghq.com` in URLs
Dynatrace	`PID`, `ProblemID`, `State: OPEN/RESOLVED`
AppDynamics	`event_type: POLICY_*`, `health_rule_name`
New Relic	`issueId`, `newrelic.com` in URLs

If no specific source is detected, the Custom transformer handles the webhook.

Alert Processing Pipeline

Webhook Received
       ↓
Token Validation
       ↓
Auto-Detect Source Type
       ↓
Transform to Canonical Format
       ↓
Apply Severity Mapping
       ↓
Apply Enrichment
       ↓
Create/Update Incident
       ↓
Trigger Escalation

Best Practices

Use Descriptive Names

Name integrations clearly: “Production Prometheus - EU”, “Staging Datadog”

Test Before Production

Send test alerts to verify configuration before relying on the integration

Configure Severity Mapping

Map severities to ensure proper prioritization of incidents

Add Enrichment for Routing

Use enrichment to add tags that routing rules can match against

Monitor Integration Health

Check event counts and error statistics regularly

Secure Webhook URLs

Treat webhook URLs like passwords—don’t commit them to public repositories

Troubleshooting

Alerts not appearing

Verify the integration is Active 2. Check the webhook URL is correct in your monitoring tool 3. Look for errors in the integration statistics 4. Verify your monitoring tool can reach the webhook URL

Wrong severity assigned

Check severity mapping configuration 2. Verify the source field name matches your payload 3. View webhook samples to see actual field values 4. Set appropriate default severity

Duplicate incidents

Verify your monitoring tool sends unique event IDs 2. Check deduplication settings 3. Review the event ID field mapping

Integration showing errors

Check the last error message 2. Verify payload format matches expected structure 3. Look at webhook samples for malformed data 4. Regenerate token if authentication issues

Rate Limits

Limit	Value
Requests per minute	1,000 per webhook
Payload size	1 MB maximum

Exceeding rate limits returns HTTP 429. Implement backoff in your monitoring tool if needed.

​Overview

Automatic Detection

Custom Mapping

Real-Time Processing

Sample Analysis

​Supported Integrations

Zabbix

Prometheus

Grafana

Datadog

Dynatrace

AppDynamics

New Relic

Custom Webhook

​How Integrations Work

​Creating an Integration

​Webhook URL Structure

​Viewing Integrations

​Integration Statistics

​Managing Integrations

​View Webhook URL

​Regenerate Token

​Activate/Deactivate

​Delete Integration

​Configuring Severity Mapping

​Standard Severity Levels

​Setting Up Mappings

​Configuring Enrichment

​Use Cases

​Adding Enrichment

​Tag-Based Routing

​How Tags Work

​Routing Examples

​Webhook Samples

​Viewing Samples

​Sample Analysis

​Auto-Detection

​Alert Processing Pipeline

​Best Practices

​Troubleshooting

​Rate Limits

Overview

Supported Integrations

How Integrations Work

Creating an Integration

Webhook URL Structure

Viewing Integrations

Integration Statistics

Managing Integrations

View Webhook URL

Regenerate Token

Activate/Deactivate

Delete Integration

Configuring Severity Mapping

Standard Severity Levels

Setting Up Mappings

Configuring Enrichment

Use Cases

Adding Enrichment

Tag-Based Routing

How Tags Work

Routing Examples

Webhook Samples

Viewing Samples

Sample Analysis

Auto-Detection

Alert Processing Pipeline

Best Practices

Troubleshooting

Rate Limits