How to Troubleshoot Agent

Agent Files

Configuration

Agent reads its configuration files from:

• /etc/glouton/glouton.conf
• /etc/glouton/conf.d/*.conf
• etc/glouton.conf
• etc/conf.d/*.conf
• C:\ProgramData\glouton\glouton.conf
• C:\ProgramData\glouton\conf.d

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

Diagnostic page

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 developper.

Logs

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:

• On Linux, when agent is installed with package or with the standard method, logs are in syslog (usually /var/log/syslog or /var/log/messages).
• On Windows, logs are usually in C:\ProgramData\glouton\logs.
• Using docker logs for Docker images

The log destination is set in the configuration files. For example in case of system installation, logging is setup in /etc/glouton/conf.d/05-system.conf:

logging:
  output: syslog

For more details, add the following to your configuration (/etc/glouton/conf.d/90-custom.conf) to increase log level to DEBUG:

logging:
  level: DEBUG

After the configuration change, you need to restart the agent (using systemctl restart glouton or docker restart glouton).

State

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 /var/lib/glouton/state.json