How RMON works

Overview

RMON gives you one place to configure checks, choose where they run, review current and historical results, publish status pages, and send notifications.

You work with monitoring through the RMON web interface. RMON takes care of sending each check to the selected monitoring location and collecting the result.

Install and manage agents from RMON after preparing their hosts, SSH access and result-delivery connection. Follow the agent setup guide for prerequisites.

From a check to an alert

1. Configure: create a check and define what a successful result looks like.
2. Choose locations: select an agent, country, region, or all available regions.
3. Run: the selected agent performs the check at the configured interval.
4. Collect: RMON receives the result and updates the dashboard and recorded measurements.
5. Evaluate: retries, expected values, and thresholds determine whether the service is healthy.
6. Inform: RMON displays the state and sends alerts through the channels assigned to the check.

If the service recovers, the current state and its history are updated and the alert can be resolved in the selected notification channel.

Agents and locations

An agent represents a location from which checks are performed. For example, you can monitor the same website from an office, a data center, and an external region.

• Agent: one specific monitoring location.
• Country: one assigned agent in each available region of a selected country.
• Region: one assigned agent in each selected region.
• All regions: all currently available regional locations.

Running a check from several places helps distinguish a local connectivity problem from a service-wide incident. Give agents and locations clear names so users can immediately understand where a failed result came from.

For the user workflow, see Agents and Countries and regions.

Overview page

Open Overview in the main menu for the installation's host and service summary. The page includes server status, RMON service status and CPU and RAM charts for RMON. Use the refresh control on a card to request current information.

Administrators also see user information and recent RMON logs. A superAdmin sees additional group, role and subscription information. Links to administrative actions depend on your role; use Admin area to manage resources and Logs to investigate failed actions.

Use Dashboard for the availability of monitored websites and services. Check the time of the latest result as well as its status, especially after an agent or receiver interruption.

Where results appear

• Dashboard: the current condition of monitored services and the locations reporting it.
• Check details and charts: current and recorded measurements, availability and response-time graphs, route data where available, and check settings.
• History: incidents and recorded status changes. Open the alerts-history action for a check to focus on its incidents; use its charts to inspect individual measurements over time.
• Notifications: incident and recovery messages delivered to the configured channels.
• Status pages: a shareable view containing only the checks you choose.

See Read check results, Notifications and alerting, and Status pages for the corresponding user guides.

Example: monitor a customer website

1. Create an HTTP check for the public website URL.
2. Select two or more monitoring locations that represent your users.
3. Set the expected status code and, if useful, a keyword that must appear on the page.
4. Set retries and a response-time threshold to reduce noise and highlight slow responses.
5. Assign an alert channel and add a runbook link for the team that will respond.
6. After checking the results, add the check to a customer-facing status page.

The same workflow applies to Ping, DNS, TCP, SMTP, and RabbitMQ checks: choose what to monitor, where to monitor it from, what counts as healthy, and who should be notified.