Alertmanager configurations: signl4: Difference between revisions

From wikinotes
No edit summary
 
Line 1: Line 1:
[[prometheus alertmanager]] can send alerts to [[signl4]], which is capable of phone, email, push notifications, and oncall rotations.
[[prometheus alertmanager]] can send alerts to [[signl4]], which is capable of phone, email, push notifications, and oncall rotations.
{{ WARNING |
might be account changes, but my alarms stopped being sent to my phone.<br>
let's use [[ntfy]] instead, where we have more control..
}}


= Documentation =
= Documentation =

Latest revision as of 03:16, 20 January 2024

prometheus alertmanager can send alerts to signl4, which is capable of phone, email, push notifications, and oncall rotations.


WARNING:

might be account changes, but my alarms stopped being sent to my phone.
let's use ntfy instead, where we have more control..

Documentation

official docs https://www.signl4.com/blog/portfolio_item/prometheus-alertmanager-mobile-alert-notification-duty-schedule-escalation/
webhook docs https://connect.signl4.com/webhook/docs/index.html

Configuration

  • First, register for signl4
  • Each team has a unique URL/team-key. No API key is required for alertmanager to send notifications
# /usr/local/etc/alertmanager/alertmanager.yml

route:
  group_by: ['alertname']
  receiver: 'smtp-local'
  route:
    - receiver: 'signl4'
      matchers:
        - 'severity = page'

receivers:
- name: signl4
  webhook_configs:
  - url: https://connect.signl4.com/webhook/${team_key}?ExtIDParam=groupKey&ExtStatusParam=status&ResolvedStatus=resolved
         # regular URL
         # https://connect.signl4.com/webhook/${team_key}

         # close SIGNL4 alerts once resolved in prometheus
         # https://connect.signl4.com/webhook/${team_key}?ExtIDParam=groupKey&ExtStatusParam=status&ResolvedStatus=resolved
    send_resolved: true