- Using the sidebar, navigate to Settings → Alerts
- Click the + button to add alert sources
- Select your alert source, choosing from native integrations, HTTP sources, or email sources and click Continue
- Follow the in-dashboard instructions to connect, send test alerts, and complete setup
Native integrations
Connect observability platforms, cloud providers, error tracking tools, uptime monitors, ticketing platforms and more, with pre-configured integrations. Receive alerts when metrics breach thresholds, applications throw errors, services go down, or security threats are detected.
AWS CloudWatch
AWS SNS
Azure Monitor
BugSnag
Checkly
Chronosphere
Cloudflare
Coralogix
Cronitor
Crowdstrike Falcon
Datadog
Dynatrace
Elastic
Expel
GitHub Issue
Google Cloud Platform
Grafana
Honeycomb
Jira/ITSM
Monte Carlo
Nagios Core
New Relic
Opsgenie
Panther
PagerDuty
Pingdom
Prometheus Alertmanager
PRTG
Runscope
Sentry Issues
SolarWinds AppOptics
Splunk
StatusCake
Sumo Logic
Uptime.com
Zendesk
Default HTTP sources
HTTP sources enable receiving alerts from any tool not covered by the native integrations list. Use default HTTP sources when you control the webhook payload from external tools. incident.io provides a URL endpoint where you send alerts with a custom payload structure.Expected body structure
metadata field to set alert attributes for routing and filtering. See the Alert Events API documentation for full field specifications and validation rules.
Custom HTTP sources
Use custom HTTP sources when working with tools that send webhooks with HTTP payload structures that cannot be modified. Write custom JavaScript within these sources to transform those payloads into incident.io’s expected alert format.Example payload from external tool
Your transform expression
Email sources
Send emails to a unique email address to create alerts in incident.io automatically. When you create an email source, incident.io generates a unique email address for that source:Example email address
- Monitoring tools or scripts that send email notifications but don’t support webhooks
- Customer support or internal escalations where critical emails should trigger alerts
Auto-resolve alerts
Some alert sources — such as email sources or tools that don’t send resolve payloads — will leave alerts in aFiring state indefinitely. Auto-resolve lets you set a timeout after which these alerts are automatically resolved.
When enabled on an alert source, any alert that remains in Firing status will be resolved after the configured duration. The timer starts from when the alert first fires, and the duration is selected from the Resolve after dropdown in the alert source configuration.
To enable auto-resolve:
- Using the sidebar, navigate to Settings → Alerts
- Select the alert source you want to configure
- Toggle Auto-resolve alerts on
- Under Resolve after, choose a duration from the dropdown (e.g., 3 hours)
- Click Save
Skip auto-resolve for active incidents
You can optionally enableskip auto-resolve if alert is attached to an active incident. When this toggle is on, alerts that are attached to an active incident will not be auto-resolved — even if the configured duration has elapsed. The alert will remain in Firing status for as long as the incident is active, and will only resolved as usual once the incident is no longer active. If the alert is detached from the incident the auto-resolve timer will restart.
This is useful when an alert is being actively investigated as part of an incident and you don’t want it to silently resolve while responders are still working on it.
Auto-resolve only applies to alerts created after the setting is enabled. Existing alerts that are already firing will not be affected by changes to the auto-resolve configuration.
Troubleshoot alert sources
Use the Inspect feature to diagnose payload and transformation issues. Click Inspect on any alert to view the original payload, JavaScript expressions, and extraction results. Edit attribute expressions to add fallbacks for unexpected payloads or fix catalog entry mappings.FAQs
How many alert sources can I create?
How many alert sources can I create?
Unlimited. All plans support connecting multiple monitoring tools simultaneously.
Can I modify native alert sources?
Can I modify native alert sources?
No. Native sources use fixed parsing logic. Use attribute expressions or create a custom HTTP source for custom extraction.
What happens if my monitoring tool changes its payload format?
What happens if my monitoring tool changes its payload format?
Native sources update automatically. For custom HTTP sources, update transform expressions to match the new payload structure.
Can I test alert sources without spamming my team?
Can I test alert sources without spamming my team?
Yes. Test alerts during alert source setup, and optionally create a test alert route that declines or silences all alerts.
Do alert sources support heartbeat monitoring?
Do alert sources support heartbeat monitoring?
No native heartbeat monitoring. Use third-party uptime monitoring services (Checkly, Cronitor, Uptime.com, Pingdom) with native alert sources, or send heartbeat signals via custom HTTP alert sources.
Why aren't my alerts appearing?
Why aren't my alerts appearing?
Check any of the following; wrong payload format, authentication issues, firewall blocking, or rate limiting in your monitoring tool.
Why didn't auto-resolve affect my existing alerts?
Why didn't auto-resolve affect my existing alerts?
Auto-resolve only applies to alerts created after the setting is enabled. If you have existing firing alerts, they will not be automatically resolved. You can resolve them manually from the dashboard, mobile app, or Slack/Microsoft Teams.
Which alert sources benefit most from auto-resolve?
Which alert sources benefit most from auto-resolve?
Auto-resolve is most useful for alert sources that don’t send resolve payloads, such as email sources or custom HTTP sources from tools that only send firing notifications. Sources like Datadog or Grafana typically send their own resolve events, so auto-resolve is less necessary.
What happens if an alert is attached to an active incident?
What happens if an alert is attached to an active incident?
If you have enabled
skip auto-resolve if alert is attached to an active incident, the alert will not be auto-resolved while the incident is active. Once the incident is no longer active, or the alert is detached from the incident, auto-resolve will apply as normal.