10.9Send a test alert
Send a test after you add or change a channel. It shows that alerts really arrive.
- Select alerting, then channels, then the channel.
- Select send test. The button shows "sending…" while it works.
- Read the result below the editor, then check the inbox or chat room.
| Result | What it means |
|---|---|
| ✓ test sent | The test was delivered. The subject line of the message is shown. |
| ✗ test failed | The destination refused it. The error from Slack, Teams, Discord, Telegram, PagerDuty or your server is shown. Fix the channel and test again. |
| test limit reached | You sent too many tests. Wait and try again. |
| test not sent | For example, an email channel whose address is not confirmed yet (confirm the address first). See 10.2. |
The test looks like a real alert, so you can see how alerts will look. Its monitor name is "obsrvly test — no monitor is down". Its text says "This is a test alert sent from the obsrvly dashboard. Nothing is wrong." By email, the subject is "[obsrvly] DOWN: obsrvly test — no monitor is down". The test also appears in the notification log (9.10).
Test limits#
- Up to 5 tests per channel each minute. Past that:
too many test sends to this channel: at most 5 per minute, try again shortly. - Up to 30 tests per team each hour. Past that:
too many test sends for this team: at most 30 per hour, try again later.
Use the API#
Call TestChannel in NotificationService with the channelId:
curl -s \
"$OBSRVLY_API/notification/obsrvly.v1.NotificationService/TestChannel" \
-H "Authorization: Bearer $OBSRVLY_KEY" \
-H "Content-Type: application/json" \
-d '{"channelId": "<channel-id>"}'The reply has status (sent or failed), subject, body and notificationId. When status is failed, errorMessage holds the reason. A failed delivery is a normal reply with status: "failed", not an error code.