• Github repository
• PyPI page

To monitor the servers with Shinken, Nagios or Icinga, system administrators usually configure active checks of the monitored servers. It means the monitoring system must have a direct network access to the monitored server.

With Eyepea monitoring agent, this model is reverted, it does passive checks of your monitored servers. You don't need to open an access from your monitoring system to the monitored servers.

The main use case of this tool is to monitor distant servers in a complex network where you can't connect directly for security reasons, typically with a large client. You need only to open NSCA or HTTP(S) port from the monitored server to the monitoring system.

The behaviour of this tool is simple:

1. The program is started by cron.
2. It retrieves monitoring data (1) from nagios-plugins.
3. Finally, it pushes the data (2) via NSCA (Shinken, Nagios, Icinga) or HTTP(S) (Shinken) to the monitoring server.
4. (WS-Shinken only) If the connexion between the monitored server and the monitoring system is broken, data is kept in a cache file, to be re-send the next run.

Warning: WS-Shinken support isn't finished, it will be available for 1.0.

Debian packages is the prefered method. If you use another distribution, you can use the Python package or contribute to publish a package for your distribution.

We are working to propose clean Debian packages, a first version exists in the debian/ folder.

Warning: Root rights are necessary to install config files and cron file. pip install eyepea-monitoring-agent

• Default config files location: /etc/eyepea_monitoring_agent/
• Default cron file location: /etc/cron.d/

1. Configure passive checks on your monitoring system:
   1. Shinken
   2. (PDF) Nagios
   3. Icinga
2. Configure the nagios plugins you want to use in nagios_plugins.cfg:
   1. Define the nagios plugins path with the path option in [default_settings] section.
   2. The name of each section is the nagios plugin command.
   3. Each setting is a CLI option of the nagios plugin.
3. Fill in the credidentials for your monitoring system in nsca.cfg or ws_shinken.cfg.
4. Adapt the checks frequency in: /etc/cron.d/eyepea_monitoring_agent.

Launch: eyepea_monitoring_agent --help You can override the location of each config file with a CLI parameter.

By default, it uses cron syslog and console for the logs. You can customize this behaviour in logging.ini: http://docs.python.org/library/logging.config.html#configuration-file-format

Community support is provided via Github: https://github.com/Eyepea/eyepea_monitoring_agent/issues

You must provide the error log with your issue.

If you need professional support, please contact Eyepea: http://www.eyepea.eu/

For general questions or contributions, you can contact me via my Github acccount: https://github.com/GMLudo

The Shinken community in general, and Jean Gabès in particular for his help and support.