Skip to main content
Configure your alert sources in incident.io. Alert sources are the systems that send alerts to incident.io, which can then be routed to the right people and teams.

The alert source object

id
string
required

The ID of this alert source

Example:

"01GW2G3V0S59R238FAHPDS1R66"

name
string
required

Unique name of the alert source

Example:

"Production Web Dashboard Alerts"

source_type
enum<string>
required

Type of alert source

Available options:
alertmanager,
app_optics,
azure_monitor,
azure_devops,
big_panda,
bugsnag,
checkly,
chronosphere,
cloudwatch,
cloudflare,
coralogix,
cronitor,
crowdstrike_falcon,
dash0,
datadog,
dynatrace,
elasticsearch,
email,
expel,
github_issue,
google_cloud,
grafana,
heartbeat,
http,
http_custom,
honeycomb,
icinga2,
incoming_calls,
jira,
jsm,
monte_carlo,
nagios,
new_relic,
opsgenie,
prtg,
pager_duty,
panther,
pingdom,
runscope,
sns,
sentry,
sentry_metric,
service_now,
splunk,
status_cake,
status_page_views,
sumo_logic,
uptime,
vercel,
wiz,
zendesk
Example:

"alertmanager"

template
object
required
Example:
alert_events_url
string

URL that can be used to send alert events to this source. This is only set for sources that accept webhook/HTTP events; email sources use the email_address field, and integration-based sources (like Jira) receive events through their native integrations.

Example:

"https://api.incident.io/v2/alert_events/http/01GW2G3V0S59R238FAHPDS1R66"

auto_resolve_incident_alerts
boolean

Whether alerts from this source keep counting down to auto-resolve while attached to an incident. Defaults to true. Has no effect without auto_resolve_timeout_minutes.

Example:

false

auto_resolve_timeout_minutes
integer<int64>

When set, alerts from this source will automatically resolve after this many minutes.

Example:

1

azure_devops_options
object
Example:
email_options
object
Example:
fixed_team_id
string

When set, the team every alert from this source is attributed to. The team attribute is managed from this field: its binding is not returned in the template and cannot be edited directly.

Example:

"01G0J1EXE7AXZ2C93K61WBPYEH"

heartbeat_options
object
Example:
http_custom_options
object
Example:
jira_options
object
Example:
owning_team_ids
string[]

IDs of teams that own this alert source

Example:
rate_limit_sharding
object

Controls how this source's ingest rate limit is split into buckets.

Example:
secret_token
string

Secret token used to authenticate this source, if applicable. If applicable, this is the token that must be included in either the query string or the 'Authorization' header when sending events to this alert source.

Example:

"some-secret-token"