Diagnostic checklist
Find where readings or notifications stop before changing multiple settings.
On this page
What you need
Access to your sender and monitor. For an agent, use status and doctor.
How to do it
- Check that your sender is running, can reach MetriBeacon over HTTPS and has a correct clock.
- Check the key, target monitor and series, then read the request's HTTP status and error code. Look at Usage for reached limits.
- Check the latest value and history. For alarms, then check the condition, current data, destination and delivery history.
Good to know
A running program does not confirm received readings. HTTP 202 confirms a started background job, not a completed result. A sent notification still needs to be checked in your inbox or chat.
If something goes wrong
Change one confirmed cause at a time. If you need help, use the contact form with the time and request ID, but no keys, tokens or private identity file.
Related guides
- Update, diagnose and remove the agent
Check the agent's status, update it or remove its local service.
- HTTP errors and retries
Decide whether an API request needs correction or a delayed retry.
- Incidents and delivery history
Check a problem's timeline separately from the delivery of its messages.