Skip to main content
PUT
Error

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Alert ID

Body

application/json

At least one of "channel" or "channels" must be provided. Sending both is allowed only when "channel" matches the first entry of "channels", so a response body can be echoed back unchanged. Responses always include both, with "channel" mirroring the first entry of "channels". Updates replace the alert's configuration rather than merging it: sending only the legacy "channel" field for an alert that has several channels reduces it to that one channel. Fetch the alert and resend the complete "channels" array to preserve them.

threshold
number
required

Threshold value for triggering the alert. For between and not_between threshold types, this is the lower bound.

Example:

100

interval
enum<string>
required

Evaluation interval for the alert.

Available options:
1m,
5m,
15m,
30m,
1h,
6h,
12h,
1d
Example:

"1h"

thresholdType
enum<string>
required

Threshold comparison direction.

Available options:
above,
below,
above_exclusive,
below_or_equal,
equal,
not_equal,
between,
not_between
Example:

"above"

dashboardId
string | null

Dashboard ID for tile-based alerts.

Example:

"65f5e4a3b9e77c001a567890"

tileId
string | null

Tile ID for tile-based alerts. Must be a line, stacked bar, or number type tile.

Example:

"65f5e4a3b9e77c001a901234"

savedSearchId
string | null

Saved search ID for saved_search alerts.

Example:

"65f5e4a3b9e77c001a345678"

groupBy
string | null

Group-by key for saved search alerts.

Example:

"ServiceName"

chartConfig
object

Chart configuration for inline alerts. Required when source is "inline" and rejected otherwise. Returned on single-alert responses (GET by ID, POST, PUT); the list endpoint omits it.

thresholdMax
number | null

Upper bound for between and not_between threshold types. Required when thresholdType is between or not_between, must be >= threshold.

Example:

500

scheduleOffsetMinutes
integer | null

Offset from the interval boundary in minutes. For example, 2 with a 5m interval evaluates windows at :02, :07, :12, etc. (UTC).

Required range: x >= 0
Example:

2

scheduleStartAt
string<date-time> | null

Absolute UTC start time anchor. Alert windows start from this timestamp and repeat every interval.

Example:

"2026-02-08T10:00:00.000Z"

source
enum<string>

Alert source type (tile-based or saved search).

Available options:
saved_search,
tile,
inline
Example:

"tile"

channel
object

First notification channel, mirrored from "channels" for pre-multi-channel clients.

channels
object[]

All notification channels to trigger when the alert fires or resolves.

Required array length: 1 - 10 elements
name
string | null

Alert name template (Handlebars), rendered as the notification title. When omitted, a default title is generated from the display name, value and threshold.

Example:

"Errors for {{group}} hit {{value}}"

displayName
string | null

Display name shown in the alerts list and in notification titles. Defaults to the name of the referenced saved search, dashboard tile, or inline chart when omitted or null.

Required string length: 1 - 512
Example:

"Checkout error spike"

tags
string[] | null

Tags for the alert. Defaults to the tags of the referenced saved search or dashboard when omitted or null; inline alerts have no parent to inherit from and default to an empty list.

Maximum array length: 50
Maximum string length: 32
Example:
message
string | null

Alert message template.

Example:

"Test Alert Message"

note
string | null

Freeform note for the alert. Supports markdown formatting.

Required string length: 1 - 4096
Example:

"Threshold raised from 50 to 100 on 2026-01-15. See [runbook](https://wiki.example.com/runbook)."

numConsecutiveWindows
integer | null

Fire the alert only after its condition has been met for this many consecutive evaluation windows. While the condition is met but fewer than this many consecutive windows have violated, the alert is in the PENDING state.

Required range: x >= 1
Example:

3

Response

Successfully updated alert

data
object

The alert object.

Last modified on September 5, 2026