Skip to main content
Different monit-agent configuration changes take effect in different ways. This guide explains when to reload, when to restart, and how to confirm that monitoring objects have been onboarded successfully.

​
Configuration reload rules

Send SIGHUP:
Restart the service:
If you only add or adjust object configuration in agent.yaml, use SIGHUP reload first. Restart is needed only when startup parameters or service-level parameters change.

​
Verify successful onboarding

After the Agent starts, a host object usually appears on the monitoring object page within a few seconds. If the page is still empty, check the following in order:
1

Check whether the Agent is running

2

Check whether the Edge address is correct

Make sure the address includes ws:// or wss://, and confirm that the Edge for the current tenant is online.
3

View Agent logs

4

Check agent.yaml

If agent.yaml was modified, confirm that the file has no YAML syntax errors.

​
Checks when objects do not appear

  1. Onboard only the host object first.
  2. After the host appears in the console, gradually add database objects such as MySQL, Redis, and PostgreSQL.
  3. After each object appears, enable controlled query tools such as mysql.query, redis.command, postgres.query, mongodb.command, and elasticsearch.cat only when needed.

Monitoring Objects Overview

Learn how monitoring objects and monit-agent work.

Configure Monitoring Objects

View configuration examples and recommendations for each object type in agent.yaml.