Overview
Integrations connect EasyContact to your monitoring and observability tools. When an alert fires in your monitoring system, it’s sent to EasyContact via webhook, automatically creating an incident and triggering the appropriate escalation policy.Automatic Detection
EasyContact 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
EasyContact 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
1
Create Integration
Add a new integration in EasyContact and select the source type
2
Copy Webhook URL
Get the unique webhook URL generated for this integration
3
Configure Source
Set up your monitoring tool to send alerts to the webhook URL
4
Test & Verify
Send a test alert and verify it appears in EasyContact
5
Configure Mappings
Optionally customize severity mapping and add enrichment data
Creating an Integration
1
Navigate to Integrations
Go to Configuration → Integrations
2
Click Add Integration
Click the Add Integration button
3
Select Type
Choose the integration type that matches your monitoring tool
4
Enter Details
- Name — Descriptive name (e.g., “Production Prometheus”)
- Description — Optional explanation
5
Save and Copy URL
Save the integration and copy the webhook URL from the dialog
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:webhookToken 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
Activate/Deactivate
Toggle integration status without deleting:- Click the three-dot menu
- Select Activate or Deactivate
Delete Integration
- Click the three-dot menu
- Select Delete
- Confirm deletion
Configuring Severity Mapping
Map source severity values to EasyContact’s standard levels.Standard Severity Levels
| Level | Description | Color |
|---|---|---|
| Critical | Requires immediate attention | Red |
| High | Serious issue, respond quickly | Orange |
| Warning | Potential issue, investigate | Yellow |
| Info | Informational alert | Blue |
| OK | Recovery/resolved state | Green |
Setting Up Mappings
1
Open Configuration
Click three-dot menu → Configure Mappings
2
Set Source Field
Enter the field name your tool uses for severity (e.g., “priority”, “level”)
3
Add Mappings
Map each source value to a standard severity:
- “P1” → Critical
- “P2” → High
- “P3” → Warning
4
Set Default
Choose the fallback severity for unmapped values
Example: Datadog Priority Mapping
Example: Datadog Priority Mapping
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
1
Open Configuration
Click three-dot menu → Configure Mappings → Enrichment tab
2
Add Key-Value Pairs
Enter the key and value for each enrichment field
3
Save Changes
Click Save to apply
Example: Production Environment Enrichment
Example: Production Environment Enrichment
Webhook Samples
EasyContact 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
EasyContact 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 |
Alert Processing Pipeline
Best Practices
Use Descriptive Names
Use Descriptive Names
Name integrations clearly: “Production Prometheus - EU”, “Staging Datadog”
Test Before Production
Test Before Production
Send test alerts to verify configuration before relying on the integration
Configure Severity Mapping
Configure Severity Mapping
Map severities to ensure proper prioritization of incidents
Add Enrichment for Routing
Add Enrichment for Routing
Use enrichment to add tags that routing rules can match against
Monitor Integration Health
Monitor Integration Health
Check event counts and error statistics regularly
Secure Webhook URLs
Secure Webhook URLs
Treat webhook URLs like passwords—don’t commit them to public repositories
Troubleshooting
Alerts not appearing
Alerts not appearing
- Verify the integration is Active
- Check the webhook URL is correct in your monitoring tool
- Look for errors in the integration statistics
- Verify your monitoring tool can reach the webhook URL
Wrong severity assigned
Wrong severity assigned
- Check severity mapping configuration
- Verify the source field name matches your payload
- View webhook samples to see actual field values
- Set appropriate default severity
Duplicate incidents
Duplicate incidents
- Verify your monitoring tool sends unique event IDs
- Check deduplication settings
- Review the event ID field mapping
Integration showing errors
Integration showing errors
- Check the last error message
- Verify payload format matches expected structure
- Look at webhook samples for malformed data
- Regenerate token if authentication issues
Rate Limits
| Limit | Value |
|---|---|
| Requests per minute | 1,000 per webhook |
| Payload size | 1 MB maximum |