Notification channels

The seven ways Glowo can reach you, and how to scope each one so the right alerts reach the right people.

A channel is one destination for alerts. You create it once, subscribe it to the events you care about, and attach it to monitors.

The seven types

Settings every channel shares

Scoping

This is the difference between a monitoring system people trust and one they mute.

• No scoping — the channel receives its subscribed events from every monitor in the workspace. Fine for a team-wide Slack channel; wrong for SMS.
• monitorIds — only these monitors.
• projectIds — every monitor in these projects. Better than listing monitors individually, because a monitor added to the project later is covered automatically.

Prefer project scoping. Monitor-level lists silently go stale as your infrastructure grows, and nobody notices until an alert does not arrive.

Enabling and disabling

A channel can be disabled without deleting it, which keeps its configuration and history. Use it to silence a noisy integration while you fix it.

Testing

Every channel has a Test action that sends a sample notification using the real configuration and delivery path. Use it whenever you create a channel — a typo’d webhook URL or a revoked bot token is silent until the first real outage, which is the worst possible moment to find out.

Choosing a set

A workable pattern for a small team:

The MONITOR_UP subscriptions matter. Without them nobody learns that the incident ended, and people keep investigating a resolved problem.