Agent reads its configuration files from:
Default installation creates the following files:
/etc/glouton/glouton.conf: common default configuration and description of some customizable option.
/etc/glouton/conf.d/05-system.conf: default option for integration with system. For example it includes syslog logger.
/etc/glouton/conf.d/30-install.conf: credentials used to communicate with Bleemeo Cloud platform.
For more details on configuration files, see Configuration
Bleemeo agent have a built-in web server, which provide a diagnostic page, available by default at http://localhost:8015/diagnostic
This page may helps you finding the issues you had.
It also provide a diagnostic archive, which contains more details, including recent debug log messages. This archive is primary targeted for Bleemeo support or Bleemeo agent developer.
In case of trouble, the most valuable source of information is the log file.
Log messages may be at various locations, depending how you run the agent:
docker logsfor Docker images
The log destination is set in the configuration files. For example in case
of system installation, logging is setup in
For more details, add the following to your configuration (
to increase log level to DEBUG:
After the configuration change, you need to restart the agent (using
systemctl restart glouton or
docker restart glouton).
Agent is stateful. It keeps in a state file some information specific to the server which run it. For example its registration ID, the metrics seen and the metrics registered with Bleemeo Cloud platform.
The state file is usually stored in
If you want to add a new proprietary MIB to your snmp agents, you need to send an email with the snmpwalk file to email@example.com generated by the following command:
$ snmpwalk -v2c -c public -ObentU DEVICE_IP 1.3.6 > ./public.snmpwalk