An incident and a delivered message are different
A monitoring rule can open an incident without its notification reaching you. Conversely, a successful channel test says nothing about whether the right rule is active. Useful monitoring alerts need both a sensible condition and a working delivery path.
MetriBeacon supports email and Telegram notification destinations. Begin with one destination you control, test it and assign it to a rule whose meaning you can explain in one sentence. That is a stronger starting point than enabling every available alarm.
Connect email deliberately
Use the notification settings to add and confirm an email destination. Follow the confirmation flow before selecting it for operational alerts. Confirmation proves access to that destination; it should not be confused with an actual incident notification.
Send a channel test and check the mailbox, including its spam folder. Then perform a controlled rule test with a harmless source. The first test checks delivery. The second checks whether observation, evaluation, incident creation and delivery work together.
Connect a private Telegram chat
Start the Telegram connection from MetriBeacon's settings. Use the provided link to the @MetriBeaconBot conversation and complete the /start step within the stated connection window, currently ten minutes. Use the generated connection link rather than sharing its binding information.
The supported destination is a private chat, not a Telegram group. Once connected, send a test message and select the destination in the relevant rule. A connected chat alone does not mean every rule will send there. The email and Telegram guide describes both confirmation paths.
Choose a condition that matches the failure
| Question | Appropriate kind of evidence |
|---|---|
| Is my endpoint responding as expected? | HTTP availability or content result |
| Has this source stopped reporting? | Missing heartbeat or missing value |
| Is a measured number too high or low? | Numeric threshold with suitable timing |
| Did my scheduled task fail to run or finish? | Job execution and schedule expectations |
For a numeric rule, choose both an opening and a clearing condition. Hysteresis keeps small changes around one boundary from repeatedly opening and closing the same incident. A duration condition can require sustained evidence rather than reacting to one sample. Missing data needs its own rule rather than an invented numeric value.
Test one rule from beginning to end
- Confirm that the source normally reports valid observations.
- Configure a rule and select the confirmed destination.
- Trigger a safe test condition or use a dedicated test monitor.
- Inspect the resulting incident and its delivery record.
- Restore the normal condition and check recovery.
- Adjust the rule if ordinary behaviour creates unnecessary messages.
Use the numeric hysteresis documentation for threshold timing and the incident delivery documentation to interpret the result. Test messages and real notifications remain separate evidence.
Handle planned work without losing context
Use a maintenance window for planned work and review its scope. Muting a notification, acknowledging an incident and scheduling maintenance serve different purposes. None should be treated as proof that the underlying system is healthy.
Keep an explanation with operational decisions where the interface offers it. When a colleague sees a muted rule or an acknowledged incident, they should understand what action is already under way and when to check again.
Account for budgets and failed delivery
Notification limits apply across the account and channels. Repeatedly pressing a test button can consume a test allowance without proving more. The current documented allowance is ten channel tests per account per hour; check the usage view and current documentation for effective limits.
When delivery fails, inspect the destination's confirmation and connection state and the recorded failure. Do not recreate a monitor merely because its message was not delivered. Separate the observed problem from the notification path.
Frequently asked questions
Does confirming my email enable every alert?
No. Confirm the destination and select it for the rules you want. A rule still needs valid conditions and observations.
Can I use a Telegram group?
The documented integration connects a private chat. Do not assume a group invitation creates a supported destination.
Will a channel test open an incident?
It tests messaging. A controlled source or rule test is needed to check incident evaluation and recovery.
Start with an actionable message
Create a free account and set up one source with one meaningful rule. For a public website, the Website/API template below provides a practical starting point. Confirm delivery before adding more rules, and give each message a clear reason to reach you.
