Axiom alert integration

Use an Axiom custom webhook notifier to send monitor alerts to Flashduty On-call. Axiom identifies a monitor by .MonitorID, and with Notify by group turned on the notification also carries the group values. Flashduty builds the Alert Key from the monitor ID plus the group values, so the trigger and recovery notifications of one monitor (or one group) update the same Flashduty alert.

Configure Axiom

Create a custom webhook notifier in Axiom

The Custom Webhook notifier is not available on Axiom’s free Personal plan: it is greyed out in the notifier list. Use a paid Axiom plan.

Where: Axiom › Monitors › Manage notifiers › New notifierOn the Monitors tab, click Manage notifiers in the top right (you can also click New monitor or open an existing monitor first), then click New notifier in the top right.

Field	Value
Name (required)	`Flashduty`
Type (required)	`Custom Webhook`
Webhook URL (required)	`{integration_url}`
Body (optional)	Keep Axiom’s default template unchanged. If you edited it before, replace it with the template below
Headers (optional)	None needed

Click Create.Axiom’s default template is shown below; Flashduty parses this structure:

{
  "action": "{{.Action}}",
  "event": {
    "monitorID": "{{.MonitorID}}",
    "body": "{{.Body}}",
    "description": "{{.Description}}",
    "queryEndTime": "{{.QueryEndTime}}",
    "queryStartTime": "{{.QueryStartTime}}",
    "timestamp": "{{.Timestamp}}",
    "title": "{{.Title}}",
    "value": {{.Value}},
    "matchedEvent": {{jsonObject .MatchedEvent}},
    "groupKeys": {{jsonArray .GroupKeys}},
    "groupValues": {{jsonArray .GroupValues}}
  }
}

Keep action, event.monitorID, event.groupKeys, and event.groupValues. Flashduty rejects a request without monitorID because it could not match the recovery to the original alert. action accepts only Open and Closed.

Add the notifier to monitors in Axiom

Where: Axiom › Monitors › New monitor (or an existing monitor) › Add notifier

Field	Value
Notifier (required)	`Flashduty`
Notify by group (optional)	Recommended when the query groups by a non-time field, see below

Open Monitors, then edit a monitor or click New monitor
Click Add notifier and select Flashduty
Save the monitor

When a threshold or anomaly monitor’s query groups by a non-time field, turn on Notify by group: each group that crosses the threshold triggers and recovers on its own, and becomes a separate alert in Flashduty.

Turn on auto-close for match monitors in Flashduty

Where: Flashduty console › Channels › Configuration › Settings › Advanced Settings

Field	Value
Auto-close timeout (required)	On
Timing start (required)	`Incident trigger`
Timeout (required)	`1 hour` (suggested)

A match monitor sends an Open notification for every matching event and never sends Closed. Notifications from one match monitor merge into one Flashduty alert, but that alert does not recover on its own. If the channel receives match monitor alerts, turn on the auto-close timeout, set the timing start to Incident trigger, and set the timeout to 1 hour.

Trigger an alert and verify the lifecycle

Where: Axiom › MonitorsMake a threshold monitor’s condition actually hold (for example, lower the threshold temporarily) and confirm that Flashduty receives an active alert. Then restore the threshold, wait for the monitor’s next run, and confirm that the alert recovers. Axiom sends one notification when a monitor enters the alert state and one when it exits, with nothing in between.After a few seconds, go back to Flashduty. If the integration shows a Latest event time, the setup works.

Alert key

Flashduty builds the Alert Key from event.monitorID. When the notification carries groups (event.groupKeys is not empty), the group names and values are part of the Alert Key too. Axiom’s documentation defines .MonitorID as the unique identifier of the monitor the notification belongs to; with Notify by group on, each group triggers separately and the notification carries that group’s values.

The Open and Closed notifications of one monitor (or one group) update the same Flashduty alert
Different groups of one monitor are different Flashduty alerts
Changes to the monitor name, description, current value, or times do not change the Alert Key

Status and severity

Axiom notifications carry no severity, so Flashduty sets every Axiom alert to Critical. To use another severity, adjust it by the check or monitor_id label with an Alert Pipeline.

`action`	Flashduty handling
`Open`	Triggers or updates the alert with severity Critical
`Closed`	Recovers the original alert
Empty or any other value	Rejects the request

Labels

Label	Source
`check`	Monitor name (`event.title`)
`monitor_id`	`event.monitorID`
`monitor_description`	Monitor description
`action`	`Open` or `Closed`
`value`	Query value at trigger or recovery (threshold and anomaly monitors only)
`query_start_time`, `query_end_time`	Query time range of the run
`group_keys`, `group_values`	Group names and values (with Notify by group)
Group names	One label per group name, set to the group value
Matched event fields	Top-level fields of the event a match monitor matched

The alert description is the notification’s event.body: for a threshold monitor, the current value compared with the threshold; for a match monitor, the matched event.

Troubleshooting

Flashduty returns a parameter error: confirm the body is still the default template above and monitorID and action are not empty
The alert does not recover: match monitors send no recovery, so turn on auto-close. A threshold monitor sends Closed only when a later run no longer crosses the threshold
Several groups merged into one alert: confirm Notify by group is on for the monitor. Without it, Axiom notifies for the monitor as a whole

For more information, see the Axiom documentation: Custom webhook notifier, Threshold monitors, and Match monitors.

Quick Start

Product Comparison

Channels

Incident Management

Post-Mortem

Status Page

Analytics

Integration Settings

Configuration

Advanced

Integrations

Best Practices

In Flashduty On-call

Use a dedicated integration

Use a shared integration

Configure Axiom

Alert key

Status and severity

Labels

Troubleshooting