Troubleshoot alert and notification delivery
If you expected an email, Discord message, or webhook post and did not get one, first separate three cases: the rule has not fired yet, the rule fired but had nowhere to send, and CloudStats attempted a send that you cannot see downstream.
Updated Nov 8, 2026
On this page
Summary#
If you expected an email, Discord message, or webhook post and did not get one, first separate three cases: the rule has not fired yet, the rule fired but had nowhere to send, and CloudStats attempted a send that you cannot see downstream. This page covers alert and notification delivery. For install failures, an inactive agent, or empty charts, start with Troubleshooting.
Prerequisites#
- Access to the CloudStats app
- The alert rule and notification channels you are investigating
- For agent-contact problems, access to the Linux host so you can check
cloudstats-agentas described in Service, status, and logs
Steps#
Work through these checks in order.
- Confirm the rule type and condition. A metric rule compares one metric to one threshold for the configured duration. An availability rule watches agent contact, not ping. See Create and manage metric alert rules and Server availability alerts.
- Check the duration. If the condition has not lasted the configured number of seconds, CloudStats has not fired yet. If the condition cleared before that duration elapsed, CloudStats does not send an alert and does not send a resolved notice.
- Check whether the rule already fired and is still active. While a metric condition stays true, or while a server stays down, CloudStats does not keep resending the same notice.
- Check notification channels on the rule. If the rule has no channels, CloudStats does not send email, Discord, or webhook notifications. Attach at least one channel if you want delivery. See Notification channels.
- Check the channel configuration. - Email: confirm the address on the channel. - Discord or webhook: confirm you saved an HTTPS URL, and that the URL is still valid and publicly reachable. CloudStats does not deliver to private, loopback, or instance-metadata addresses.
- Send a test from the channel if the app offers one. A completed test means CloudStats attempted delivery. It does not guarantee that your email provider, Discord, or webhook receiver has already shown the message.
- For availability surprises, compare app status with the rule duration. The app can mark a server offline after 60 seconds without contact, before an availability alert fires.
- For contact problems, check the agent with the commands in Troubleshooting. The host must reach
https://api.cloudstats.me.
Expected behavior#
- No channels on a rule means no notification sends, even if the rule evaluates.
- Duration
0can fire on the first matching sample (metric) or as soon as the agent is treated as out of contact (availability). A longer duration delays the first notice. - One firing notice and, after recovery, one resolved or server-recovered notice. No separate cooldown period after recovery.
- A test can report that the dispatcher did not complete the test in time. That means CloudStats did not finish the test attempt in the allowed window. It is not a promise about downstream inbox speed.
Troubleshooting and limitations#
| Symptom | What to check |
|---|---|
| No mail, Discord message, or webhook when you expected an alert | Duration, channels on the rule, and whether the condition actually stayed true long enough |
| Server shows offline but no server-down notice | Rule duration versus the 60-second online window; channels on the availability rule; whether the agent later resumed contact in time |
| Repeated problem, but only one notice | Expected while the same alert stays active |
| Test completed, inbox still empty | Spam or filtering; the address or webhook URL; that a completed test is not a downstream delivery guarantee |
| Test says the dispatcher did not complete the test in time | Try the test again later. This page does not promise how long delivery should take |
| Discord or webhook never arrives | Use HTTPS; confirm the URL is public and current; check that your receiver accepts the JSON POST |
| Email never arrives | Confirm the channel address; check spam and forwarding; do not assume a provider inbox delay |
Limitations of the current product:
- CloudStats notification channel types are email, Discord, and webhook. Slack and Telegram are not available.
- This page cannot promise that a third-party inbox will accept or display a message.
- Do not share your password, Discord webhook URL, reset link, or other secrets in a ticket unless a human support person has asked for a specific safe detail.
If you cannot sign in to check rules or channels, see Account sign-in and password reset and contact CloudStats support rather than sending credentials.