Agents

What are agents?

An RMON Agent is a monitoring location that performs the checks assigned to it. RMON collects the results, updates the dashboard and history, and sends notifications when a check requires attention.

Agents are installed and managed from the RMON web interface. You do not need to download, install, or configure an agent separately.

• One agent can perform multiple checks.
• Only one RMON Agent can be added to an individual server.
• Agents can represent offices, data centers, cloud regions, or other useful monitoring locations.
• Guest users cannot manage agents or open the Agents section.

For a high-level view of the full monitoring flow, see How RMON works.

Add an agent

1. Create and configure the target server in Admin area → Servers.
2. Open Monitoring → Agents.
3. Click Add Agent and select the target server.
4. Enter a recognizable agent name, select its location settings, and add a useful description.
5. Enable the agent when it should start performing assigned checks.
6. Save the form. RMON performs the installation and adds the agent to the Agents page.

Use names such as Frankfurt external or Office network so users can immediately understand where a check result was produced.

Always add and install agents through RMON. Separate agent installation is not part of the user workflow.

Manage agents

Open an agent on the Agents page to review its assigned checks and resource usage. Depending on your permissions, the available actions let you start, restart, stop, edit, or delete the agent.

• Start: make an installed, stopped agent available for checks.
• Restart: restart the agent after a configuration change or when troubleshooting.
• Stop: temporarily prevent the agent from running its assigned checks.
• Edit: change the user-facing name, location, availability, sharing, or description.
• Delete: remove an agent that is no longer needed.

Before stopping or deleting an agent, move important checks to another monitoring location so you do not create gaps in monitoring.

Assign checks

1. Open the Dashboard and click Add check, or edit an existing check.
2. In Place, select Agent and add one or more agents with the + button.
3. Configure the selected check type: DNS, Ping, TCP, HTTP(s), RabbitMQ, or SMTP.
4. Select notification channels if the check should alert Telegram, Slack, PagerDuty, Mattermost, IncidentRelay, and/or Email.
5. Save the check and verify that results appear for every selected agent.

See Assign checks and Countries and regions for more user examples.

Review results

Each result is associated with the agent that performed the check. Compare locations on the dashboard and in check history to determine whether a problem is local or affects the monitored service everywhere.

HTTP checks can also display response timing stages such as DNS lookup, connection, secure connection, first response, redirects, and download time. These values help users identify which part of a request became slow without needing access to agent internals.

For result states and history, see Read check results.