How to Troubleshoot Agent

Agent Files


Agent reads its configuration files from:

  • /etc/bleemeo/agent.conf

  • /etc/bleemeo/agent.conf.d/*.conf

  • etc/agent.conf

  • etc/agent.conf.d/*.conf

Default installation creates the following files:

  • /etc/bleemeo/agent.conf: common default configuration and description of some customizable option.

  • /etc/bleemeo/agent.conf.d/05-system.conf: default option for integration with system. For example it includes syslog logger.

  • /etc/bleemeo/agent.conf.d/30-graphite_metrics_source.conf: configuration of metrics source (only Telegraf is supported).

  • /etc/bleemeo/agent.conf.d/30-install.conf: credentials used to communicate with Bleemeo Cloud platform.

For more details on configuration files, see Agent Configuration Files


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:

  • In syslog when agent is installed with package or with the standard method.

  • 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/bleemeo/agent.conf.d/05-system.conf:

    output: syslog

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

    level: DEBUG

And restart the agent


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/bleemeo/state.json