Identify why it is obsolete
A monitor may point to a retired campaign page, an old domain or a service that moved to a new address. Record the reason it is no longer useful, not simply that it has become noisy. Before changing it, ask whether another team or client still reads its alerts or status history. A check with no recent failures may still serve an important role that is not obvious from its name.
Map the replacement
If the customer task still exists elsewhere, identify the new monitored path and its owner before retiring the old one. Confirm that the replacement condition watches the intended behavior rather than just a redirect or generic landing page. A renamed monitor is not automatically equivalent coverage. Keep the old and new responsibilities understandable in the inventory, including notification recipients and any public status-page presentation.
Preserve useful history
Decide what incident records are needed for ongoing operations or existing commitments before deleting a resource. Follow the provider’s documented export and retention options and your own information-handling rules. This guide does not prescribe legal retention periods. Avoid putting credentials or sensitive customer details into an archive merely because the monitoring tool allows free-text notes. Record the retirement date and the person who approved it.
Check the surrounding links
After the authorized change, inspect related runbooks, public status components and responder contact lists for references to the retired check. Remove misleading coverage claims rather than leaving a green-looking placeholder. Review the inventory total before using the freed capacity as a reason to downgrade a plan; other required capabilities may still matter. Finish with an explicit statement of what is now covered, what was intentionally dropped and what remains unknown.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- UptimeRobot: website monitoring — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26
- UptimeRobot: monitoring for business owners — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26