Practical monitoring guidance from RMON

Publisher and scope

RMON publishes this blog for people who configure, use and administer monitoring. Articles explain availability checks, network locations, certificates, alerts and the practical limits of those checks.

The byline “RMON” identifies the product publisher. These are product guides and worked examples, not independent product reviews. Use the linked documentation for configuration details and the changelog to check changes relevant to your version.

Examples and evidence

Example domains, fictional companies and sample dashboard values illustrate a workflow. They are not customer records, live service measurements or performance guarantees. Screenshots show an example configuration; the checks and locations in your installation will differ.

A suggested failure test describes an exercise you can reproduce on a disposable endpoint. Its expected result is a condition to verify, not a claim that the test ran in your environment. Keep the target, location, interval, retries and response conditions with any measurements you record.

For capacity planning, use measurements from your intended workload. A useful benchmark needs a software version, hardware and network details, check types and intervals, concurrency, test duration and observed results. Illustrative response times do not establish a supported number of checks.

Dates and corrections

Published dates identify the original article date. When an article receives a substantive correction or update, its Updated date appears separately. Reading time is an estimate.

If an instruction differs from your installation, contact RMON with the page URL, product and agent versions, relevant settings with secrets removed, and the expected and observed behavior. Never include passwords, tokens or private keys.

Start with the setup guide or return to all articles.