docs: Self review of doc pages
This commit is contained in:
@@ -4,8 +4,8 @@ title: Notification channels
|
||||
sidebar_label: Notification channels
|
||||
---
|
||||
|
||||
A channel is a destination for alerts. [Monitors](./monitors.md) reference
|
||||
channels by ID, so one destination serves as many monitors as you like.
|
||||
A channel is a destination for alerts. One channel serves as many
|
||||
[monitors](./monitors.md) as you like.
|
||||
|
||||
Manage them at **Settings → Notifications**.
|
||||
|
||||
@@ -64,9 +64,7 @@ Posts the alert as message content.
|
||||
|
||||
Port `465` uses implicit TLS; anything else uses STARTTLS.
|
||||
|
||||
Alert emails are rendered by the same email system that sends licence and
|
||||
account mail, so a monitor alert and an account email look like the same
|
||||
product.
|
||||
Alert emails look like the rest of the mail Vantage sends you.
|
||||
|
||||
## The message
|
||||
|
||||
@@ -83,9 +81,9 @@ something that needs to branch on status.
|
||||
## Testing
|
||||
|
||||
Every channel has a **Test** button. It dispatches a fabricated down event for a
|
||||
monitor called "Test monitor", through the real delivery path so a test that
|
||||
arrives proves the credentials, the network path and the destination, not just
|
||||
the configuration form.
|
||||
monitor called "Test monitor" and sends it the same way a real alert goes out, so
|
||||
a test that arrives proves the credentials, the network path and the destination
|
||||
as well as the form.
|
||||
|
||||
:::tip Test after every change
|
||||
Channel settings are only exercised when something breaks, which is the worst
|
||||
|
||||
Reference in New Issue
Block a user