Skip to main content

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:

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 ConfigurationIntegrations
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:
https://api.easycontact.ai/api/v1/webhooks/ingest/{webhookToken}
The 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:
ColumnDescription
NameIntegration name and description
TypeSource type badge (Zabbix, Prometheus, etc.)
EventsTotal number of events received
Last EventWhen the last event was received
StatusActive or Inactive
ActionsView 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

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

Regenerate Token

If your webhook URL is compromised:
  1. Click the three-dot menu
  2. Select Regenerate Token
  3. 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:
  1. Click the three-dot menu
  2. Select Activate or Deactivate
Inactive integrations ignore incoming webhooks.

Delete Integration

  1. Click the three-dot menu
  2. Select Delete
  3. Confirm deletion
Deleting an integration permanently invalidates its webhook URL and removes all configuration.

Configuring Severity Mapping

Map source severity values to EasyContact’s standard levels.

Standard Severity Levels

LevelDescriptionColor
CriticalRequires immediate attentionRed
HighSerious issue, respond quicklyOrange
WarningPotential issue, investigateYellow
InfoInformational alertBlue
OKRecovery/resolved stateGreen

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
{
  "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

1

Open Configuration

Click three-dot menu → Configure MappingsEnrichment tab
2

Add Key-Value Pairs

Enter the key and value for each enrichment field
3

Save Changes

Click Save to apply
{
  "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.

Webhook Samples

EasyContact stores samples of incoming webhooks for debugging and configuration.

Viewing Samples

  1. Navigate to ConfigurationWebhook Samples
  2. Filter by integration
  3. 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:
SourceDetection Signals
Zabbixevent_id, trigger_name, trigger_severity
Prometheusalerts array, status: firing/resolved
GrafanaruleId, orgId, dashboardURL
Datadogalert_id, datadoghq.com in URLs
DynatracePID, ProblemID, State: OPEN/RESOLVED
AppDynamicsevent_type: POLICY_*, health_rule_name
New RelicissueId, 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

Name integrations clearly: “Production Prometheus - EU”, “Staging Datadog”
Send test alerts to verify configuration before relying on the integration
Map severities to ensure proper prioritization of incidents
Use enrichment to add tags that routing rules can match against
Check event counts and error statistics regularly
Treat webhook URLs like passwords—don’t commit them to public repositories

Troubleshooting

  1. 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
  1. 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
  1. Verify your monitoring tool sends unique event IDs
  2. Check deduplication settings
  3. Review the event ID field mapping
  1. 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

LimitValue
Requests per minute1,000 per webhook
Payload size1 MB maximum
Exceeding rate limits returns HTTP 429. Implement backoff in your monitoring tool if needed.