The problem

In large enough environments, running versions of OP5 Monitor lower than 8.1.2, the "Maximum response size" of Livestatus may have to be increased. The symptoms of this issue are:

1. Having all values show as 0 in the web user interface.
2. A similar log message in /opt/monitor/var/livestatus.log:

   Maximum response size of 104857600 bytes exceeded!

The solution

Change the file /opt/monitor/etc/mconf/livestatus.cfg from this:

# Naemon config
broker_module=/usr/lib64/naemon-livestatus/livestatus.so hidden_custom_var_prefix=OP5SECRET_ pnp_path=/opt/monitor/op5/pnp/perfdata /opt/monitor/var/rw/live_tmp
event_broker_options=-1

To this:

# Naemon config
broker_module=/usr/lib64/naemon-livestatus/livestatus.so hidden_custom_var_prefix=OP5SECRET_ pnp_path=/opt/monitor/op5/pnp/perfdata /opt/monitor/var/rw/live_tmp max_response_size=1048576000
event_broker_options=-1

Hint: The added configuration is at the end of line 2. You may edit the value of this setting to fit your environment.

After modifying this file, restart Naemon:

systemctl restart naemon