Alertmanager

App · 10 actions

Work with Prometheus Alertmanager: silence alerts during a deploy or from a chat button, expire and list silences, list firing alerts, and send and resolve alerts of your own. Start a workflow when an alert fires or resolves, or a silence is created or about to end.

Actions

ActionWhat it does
Create silenceSilence the alerts the matchers pick for a length of time or until a moment, now or from a later start, such as during a deploy.
Expire silenceEnd a silence now, so its alerts notify again.
Get silenceGet one silence: what it matches, who created it and why, when it ends, and its state.
Get statusGet Alertmanager's version, when it started, its cluster's members and its configuration as loaded (secrets hidden).
List alert groupsList the alerts as Alertmanager groups them for notifications (by alert name, cluster or whatever its routes group by), with each group's receiver and alerts.
List alertsList the alerts firing now, newest first, with their labels, annotations and receivers: only those not silenced or inhibited, unless you choose otherwise.
List receiversList the receivers Alertmanager's configuration names: where it can send notifications, such as a team's email or Slack channel.
List silencesList silences, active ones ending soonest first: those in force or starting later, unless you choose otherwise.
Resolve alertMark a firing alert resolved now, found by its fingerprint or by the name and labels it was sent with.
Send alertSend an alert to Alertmanager, which routes it to its receivers like one from Prometheus.

Create silence

Silence the alerts the matchers pick for a length of time or until a moment, now or from a later start, such as during a deploy. They keep firing in Alertmanager but notify no one.

Inputs

MatchersmatcherstextRequired
Which alerts to silence, one matcher per line, such as alertname=DiskFull and instance=~"db-.*". An alert's labels from a trigger work too.
Fordurationtext
How long it lasts, or type one such as 90m or 1d 12h. Defaults to 2 hours.One of: 15m (15 minutes), 30m (30 minutes), 1h (1 hour), 2h (2 hours), 4h (4 hours), 8h (8 hours), 1d (1 day), 1w (1 week). Default: 2h.
Untilends_atdate and time
When it ends, instead of a length of time.
Startsstarts_atdate and time
When it starts, such as a maintenance window's start. Leave blank for now.
Created bycreated_bytext
Who it is from, shown in Alertmanager. Defaults to Lodol.
Commentcommenttext
Why, shown in Alertmanager, such as Deploying release 4.2.

Outputs

commenttext
Why it was created
created_bytext
Who created it
ends_attext
When it ends, in UTC (ISO 8601)
idtext
The silence's ID
linktext
Its page in Alertmanager
matcherslist
The alerts it silences
matchers_texttext
Its matchers on one line, comma-separated
minutes_leftnumber
Whole minutes until it ends; 0 once expired
starts_attext
When it starts, in UTC (ISO 8601)
statetext
active, pending (starts later) or expired
updated_attext
When it last changed, in UTC (ISO 8601)
Example output
{
  "comment": "Deploying release 4.2",
  "created_by": "Lodol",
  "ends_at": "2026-11-09T11:00:00.000Z",
  "id": "3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "link": "https://alertmanager.example.com/#/silences/3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "matchers": [
    "alertname=\"DiskFull\"",
    "instance=~\"db-.*\""
  ],
  "matchers_text": "alertname=\"DiskFull\", instance=~\"db-.*\"",
  "minutes_left": 120,
  "starts_at": "2026-11-09T09:00:00.000Z",
  "state": "active",
  "updated_at": "2026-11-09T09:00:00.000Z"
}

Expire silence

End a silence now, so its alerts notify again. One already ended is left as it is.

Inputs

SilencesilencetextRequired
The silence: pick it, or give its ID from Create silence, List silences or a trigger.

Outputs

already_expiredtrue/false
True when it had already ended, so nothing changed
commenttext
Why it was created
created_bytext
Who created it
ends_attext
When it ends, in UTC (ISO 8601)
idtext
The silence's ID
linktext
Its page in Alertmanager
matcherslist
The alerts it silences
matchers_texttext
Its matchers on one line, comma-separated
minutes_leftnumber
Whole minutes until it ends; 0 once expired
starts_attext
When it starts, in UTC (ISO 8601)
statetext
active, pending (starts later) or expired
updated_attext
When it last changed, in UTC (ISO 8601)
Example output
{
  "already_expired": false,
  "comment": "Deploying release 4.2",
  "created_by": "Lodol",
  "ends_at": "2026-11-09T09:30:00.000Z",
  "id": "3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "link": "https://alertmanager.example.com/#/silences/3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "matchers": [
    "alertname=\"DiskFull\"",
    "instance=~\"db-.*\""
  ],
  "matchers_text": "alertname=\"DiskFull\", instance=~\"db-.*\"",
  "minutes_left": 0,
  "starts_at": "2026-11-09T09:00:00.000Z",
  "state": "expired",
  "updated_at": "2026-11-09T09:00:00.000Z"
}

Get silence

Get one silence: what it matches, who created it and why, when it ends, and its state.

Inputs

SilencesilencetextRequired
The silence: pick it, or give its ID from Create silence, List silences or a trigger.

Outputs

commenttext
Why it was created
created_bytext
Who created it
ends_attext
When it ends, in UTC (ISO 8601)
idtext
The silence's ID
linktext
Its page in Alertmanager
matcherslist
The alerts it silences
matchers_texttext
Its matchers on one line, comma-separated
minutes_leftnumber
Whole minutes until it ends; 0 once expired
starts_attext
When it starts, in UTC (ISO 8601)
statetext
active, pending (starts later) or expired
updated_attext
When it last changed, in UTC (ISO 8601)
Example output
{
  "comment": "Deploying release 4.2",
  "created_by": "Lodol",
  "ends_at": "2026-11-09T11:00:00.000Z",
  "id": "3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "link": "https://alertmanager.example.com/#/silences/3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
  "matchers": [
    "alertname=\"DiskFull\"",
    "instance=~\"db-.*\""
  ],
  "matchers_text": "alertname=\"DiskFull\", instance=~\"db-.*\"",
  "minutes_left": 120,
  "starts_at": "2026-11-09T09:00:00.000Z",
  "state": "active",
  "updated_at": "2026-11-09T09:00:00.000Z"
}

Get status

Get Alertmanager's version, when it started, its cluster's members and its configuration as loaded (secrets hidden).

Inputs

None.

Outputs

build_datetext
When it was built
cluster_nametext
Its name in the cluster
cluster_statustext
ready, settling or disabled (when it runs on its own)
configtext
Its configuration file as loaded, with passwords and secret URLs shown as <secret>
go_versiontext
The Go version it was built with
peer_countnumber
How many members the cluster has
peerslist
The cluster's members, itself included
revisiontext
The source revision it was built from
up_sincetext
When it started, in UTC (ISO 8601)
versiontext
Alertmanager's version, such as 0.28.1
Example output
{
  "build_date": "20250307-15:05:18",
  "cluster_name": "01JQ8T2M8ZB3W8X3XW4E5G7N9H",
  "cluster_status": "ready",
  "config": "route:\n  receiver: oncall\nreceivers:\n  - name: oncall\n",
  "go_version": "go1.23.7",
  "peer_count": 1,
  "peers": [
    {
      "address": "10.0.0.5:9094",
      "name": "01JQ8T2M8ZB3W8X3XW4E5G7N9H"
    }
  ],
  "revision": "b2099eaa2c9ebc25edb26517cb9c732738e93910",
  "up_since": "2026-11-01T07:00:00.000Z",
  "version": "0.28.1"
}

List alert groups

List the alerts as Alertmanager groups them for notifications (by alert name, cluster or whatever its routes group by), with each group's receiver and alerts.

Inputs

Matchersmatcherstext
Only alerts whose labels match, one matcher per line, such as alertname=DiskFull or instance=~"web-.*" (=~ matches a pattern; != and !~ leave out). Leave blank for every alert.
Receiverreceivertext
Only alerts sent to this receiver. Leave blank for any.
Include muted groupsinclude_mutedtrue/false
Also list groups whose alerts are all silenced or inhibited. On by default.Default: true.

Outputs

alert_countnumber
How many alerts the groups hold in all
countnumber
How many groups there are
groupslist
The groups
Example output
{
  "alert_count": 1,
  "count": 1,
  "groups": [
    {
      "alert_count": 1,
      "alerts": [
        {
          "annotations": {
            "description": "/var/lib/postgresql has 2 GB left.",
            "summary": "Disk on db-1 is 95% full"
          },
          "description": "/var/lib/postgresql has 2 GB left.",
          "ends_at": "2026-11-09T08:24:30.000Z",
          "fingerprint": "5f2a8c41d9e07b36",
          "generator_url": "https://prometheus.example.com/graph?g0.expr=disk_used",
          "inhibited": false,
          "inhibited_by": [],
          "labels": {
            "alertname": "DiskFull",
            "instance": "db-1:9100",
            "job": "node",
            "severity": "critical"
          },
          "name": "DiskFull",
          "receivers": [
            "oncall"
          ],
          "severity": "critical",
          "silence_link": "https://alertmanager.example.com/#/silences/new?filter=%7Balertname%3D%22DiskFull%22%7D",
          "silenced": false,
          "silenced_by": [],
          "starts_at": "2026-11-09T08:12:30.000Z",
          "state": "active",
          "summary": "Disk on db-1 is 95% full",
          "updated_at": "2026-11-09T08:20:30.000Z"
        }
      ],
      "firing_count": 1,
      "labels": {
        "alertname": "DiskFull"
      },
      "receiver": "oncall"
    }
  ]
}

List alerts

List the alerts firing now, newest first, with their labels, annotations and receivers: only those not silenced or inhibited, unless you choose otherwise.

Inputs

Matchersmatcherstext
Only alerts whose labels match, one matcher per line, such as alertname=DiskFull or instance=~"web-.*" (=~ matches a pattern; != and !~ leave out). Leave blank for every alert.
Which alertsstatetext
Firing and not muted (the default), silenced, inhibited, either of those, or any.One of: active (Firing, not silenced or inhibited), silenced, inhibited, muted (Silenced or inhibited), any. Default: active.
Receiverreceivertext
Only alerts sent to this receiver. Leave blank for any.
How manylimitnumber
The most to list. Defaults to 100.From 1 to 1000.

Outputs

alertslist
The alerts, newest first
countnumber
How many alerts are listed
has_moretrue/false
True when more alerts matched than the limit
totalnumber
How many alerts matched, before the limit
Example output
{
  "alerts": [
    {
      "annotations": {
        "description": "/var/lib/postgresql has 2 GB left.",
        "summary": "Disk on db-1 is 95% full"
      },
      "description": "/var/lib/postgresql has 2 GB left.",
      "ends_at": "2026-11-09T08:24:30.000Z",
      "fingerprint": "5f2a8c41d9e07b36",
      "generator_url": "https://prometheus.example.com/graph?g0.expr=disk_used",
      "inhibited": false,
      "inhibited_by": [],
      "labels": {
        "alertname": "DiskFull",
        "instance": "db-1:9100",
        "job": "node",
        "severity": "critical"
      },
      "name": "DiskFull",
      "receivers": [
        "oncall"
      ],
      "severity": "critical",
      "silence_link": "https://alertmanager.example.com/#/silences/new?filter=%7Balertname%3D%22DiskFull%22%7D",
      "silenced": false,
      "silenced_by": [],
      "starts_at": "2026-11-09T08:12:30.000Z",
      "state": "active",
      "summary": "Disk on db-1 is 95% full",
      "updated_at": "2026-11-09T08:20:30.000Z"
    }
  ],
  "count": 1,
  "has_more": false,
  "total": 1
}

List receivers

List the receivers Alertmanager's configuration names: where it can send notifications, such as a team's email or Slack channel.

Inputs

None.

Outputs

countnumber
How many receivers there are
receiverslist
The receivers in Alertmanager's configuration
Example output
{
  "count": 2,
  "receivers": [
    {
      "name": "oncall"
    },
    {
      "name": "team-email"
    }
  ]
}

List silences

List silences, active ones ending soonest first: those in force or starting later, unless you choose otherwise.

Inputs

Which silencesstatetext
Active or pending (the default), only active, only pending (starting later), expired, or any.One of: current (Active or pending), active, pending (Pending (starts later)), expired, any. Default: current.
Matchersmatcherstext
Only silences of alerts with these labels, such as alertname=DiskFull. Leave blank for every silence.
Created bycreated_bytext
Only silences whose creator contains this, such as a name.
How manylimitnumber
The most to list. Defaults to 100.From 1 to 1000.

Outputs

countnumber
How many silences are listed
has_moretrue/false
True when more silences matched than the limit
silenceslist
The silences: active ones ending soonest first, then pending, then expired
totalnumber
How many silences matched, before the limit
Example output
{
  "count": 1,
  "has_more": false,
  "silences": [
    {
      "comment": "Deploying release 4.2",
      "created_by": "Lodol",
      "ends_at": "2026-11-09T11:00:00.000Z",
      "id": "3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
      "link": "https://alertmanager.example.com/#/silences/3f2a1b4c-5d6e-4f70-8a9b-0c1d2e3f4a5b",
      "matchers": [
        "alertname=\"DiskFull\"",
        "instance=~\"db-.*\""
      ],
      "matchers_text": "alertname=\"DiskFull\", instance=~\"db-.*\"",
      "minutes_left": 120,
      "starts_at": "2026-11-09T09:00:00.000Z",
      "state": "active",
      "updated_at": "2026-11-09T09:00:00.000Z"
    }
  ],
  "total": 1
}

Resolve alert

Mark a firing alert resolved now, found by its fingerprint or by the name and labels it was sent with. For alerts a workflow sent: Prometheus sends its own again while they still fire.

Inputs

AlertalerttextRequired
The alert's fingerprint (from a trigger, List alerts or Send alert), or its name, such as BackupFailed.
Labelslabelsobject
With a name: the other labels it was sent with, severity too. Leave blank for a fingerprint.

Outputs

fingerprinttext
The alert's fingerprint
labelsobject
Its labels
nametext
The alert's name
resolved_attext
When it was resolved, in UTC (ISO 8601)
was_firingtrue/false
True when it was firing and is now resolved; false when no such alert was firing, so nothing changed
Example output
{
  "fingerprint": "5f2a8c41d9e07b36",
  "labels": {
    "alertname": "DiskFull",
    "instance": "db-1:9100",
    "job": "node",
    "severity": "critical"
  },
  "name": "DiskFull",
  "resolved_at": "2026-11-09T09:02:00.000Z",
  "was_firing": true
}

Send alert

Send an alert to Alertmanager, which routes it to its receivers like one from Prometheus. Without an end, it resolves itself after 5 minutes (Alertmanager's resolve_timeout) unless sent again; use Resolve alert to end it sooner.

Inputs

Alert namealert_nametextRequired
The alert's name (its alertname label), such as BackupFailed.
Severityseveritytext
Its severity label, such as critical, warning or info, which routes often send to different receivers.
Labelslabelsobject
Other labels, such as instance db-1 and team database. The same name and labels make the same alert.
Summarysummarytext
One line on what is wrong, shown in notifications.
Descriptiondescriptiontext
More detail, shown in notifications.
Other annotationsannotationsobject
More annotations, such as runbook_url.
Startedstarts_atdate and time
When it started. Leave blank for now.
Endsends_atdate and time
When it ends by itself. Leave blank for 5 minutes after it was last sent.
Source linkgenerator_urltext
A link to what raised it, such as a dashboard or a run's page.

Outputs

annotationsobject
All its annotations, such as summary and runbook_url
descriptiontext
Its description annotation; empty when it has none
ends_attext
When Alertmanager will count it resolved unless it hears about it again, in UTC (ISO 8601)
fingerprinttext
Alertmanager's ID for the alert, worked out from its labels, such as 5f2a8c41d9e07b36
generator_urltext
A link to what raised it, such as its Prometheus graph
inhibitedtrue/false
True when another alert inhibits it
inhibited_bylist
The alerts inhibiting it
labelsobject
All its labels, such as alertname, instance and job
nametext
The alert's name (its alertname label)
receiverslist
Where Alertmanager sends it
severitytext
Its severity label, such as critical; empty when it has none
silence_linktext
A link to Alertmanager's New Silence page, filled in with its labels
silencedtrue/false
True when a silence mutes it
silenced_bylist
The silences muting it
starts_attext
When it started firing, in UTC (ISO 8601)
statetext
active (firing and notifying), suppressed (silenced or inhibited) or unprocessed (just arrived)
summarytext
Its summary annotation; empty when it has none
updated_attext
When Alertmanager last heard about it, in UTC (ISO 8601)
Example output
{
  "annotations": {
    "description": "/var/lib/postgresql has 2 GB left.",
    "summary": "Disk on db-1 is 95% full"
  },
  "description": "/var/lib/postgresql has 2 GB left.",
  "ends_at": "2026-11-09T08:24:30.000Z",
  "fingerprint": "5f2a8c41d9e07b36",
  "generator_url": "https://prometheus.example.com/graph?g0.expr=disk_used",
  "inhibited": false,
  "inhibited_by": [],
  "labels": {
    "alertname": "DiskFull",
    "instance": "db-1:9100",
    "job": "node",
    "severity": "critical"
  },
  "name": "DiskFull",
  "receivers": [
    "oncall"
  ],
  "severity": "critical",
  "silence_link": "https://alertmanager.example.com/#/silences/new?filter=%7Balertname%3D%22DiskFull%22%7D",
  "silenced": false,
  "silenced_by": [],
  "starts_at": "2026-11-09T08:12:30.000Z",
  "state": "active",
  "summary": "Disk on db-1 is 95% full",
  "updated_at": "2026-11-09T08:20:30.000Z"
}

On this page