Skip to content
Go to dashboard

9.10Notification history

The notification log lists every notification obsrvly tried to send. It shows the exact message each channel received.

  1. Select alerting, then notification log.
  2. The list on the left shows each attempt: result, channel, event, subject and time.
  3. Select a row. The right side shows the details, the error if there was one, and the payload. The payload is the message exactly as the channel received it.

The log shows the newest 100 attempts and updates every 30 seconds. To see one monitor's notifications, open the monitor and look at Recent notifications.

ResultMeaning
✓ sent (delivered)The channel accepted the message.
✗ failedThe channel refused it or did not answer. The row shows the error.
– skipped (not sent)obsrvly did not send it. The row shows why.

Each row also shows the event: fire (first alert), reminder, resolved or acknowledged.

Common reasons#

MessageWhat to do
this monitor has no alert channelsAttach a channel to the monitor.
email address not confirmedConfirm the address (see 10.2).
this channel was not foundAttach a channel that still exists.
this channel's saved credentials could not be read; save the channel againOpen the channel and save it again (see 10.10).
the monitor recovered before this alert was sentNothing. The monitor recovered while the alert was held (see 9.8).
Any other textThis is the error from the channel's provider. Check the channel's settings (chapter 10).

Through the API#

Call ListNotifications. Use limit (default 50, at most 200), cursor for the next page, and monitorId to see one monitor. The API can page past 100 rows and filter by monitor. The log tab cannot.

List one monitor's notifications
bash
curl -s "$API/notification/obsrvly.v1.NotificationService/ListNotifications" \
  -H "Authorization: Bearer $OBSRVLY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"monitorId": "<monitor-id>", "limit": 50}'

Each record has event, status (sent, failed or skipped), channelName, channelType, subject, body, errorMessage and sentAt.

Why didn't I get an alert?#

  1. Open alerting → thresholds and look at why didn't I get paged? (see 9.2). It shows, for example, too few failed checks in a row, an open incident, the cooldown, a mute or a maintenance window.
  2. Open alerting → notification log. Check whether the alert was sent, failed or skipped.
  3. Check that the monitor has alert channels attached.
  4. For email, check that the address is confirmed (see 10.2) and look in your spam folder.

Last updated