Monitoring Rudder itself

Monitoring a Node

The monitoring of a node mainly consists in checking that the Node can speak with its policy server, and that the agent is run regularly.

A good place to start is to check the content of the last run log file. It can be found in /var/rudder/cfengine-community/output/previous.

You can search lines containing FATAL:, Fatal :, or could not get an updated configuration with a log monitoring tool to automatically detect communication issues with the policy server.

To get the last run time, you can lookup the modification date of /var/rudder/cfengine-community/last_successful_inputs_update.

Monitoring a Server

You can use use regular API calls to check the server is running and has access to its data. For example, you can issue the following command to get the list of currently defined rules:

curl -X GET -H "X-API-Token: yourToken" http://your.rudder.server/rudder/api/latest/rules

You can then check the status code (which should be 200). See the API documentation for more information.

You can also check the webapp logs (in /var/log/rudder/webapp/year_month_day.stderrout.log) for error messages.