Last week I upgraded a server to Observium 23.10.13043 (stable)
In Polling information I had a huge increase in system polling, (See attached images.)
I backed out the upgrade and tried it again a few days later, when I had more time to investigate.
In addition the processor graph had changed, showing much higher CPU usage I also noticed a new graph called Load Averages
defined here...
# svn blame /opt/observium/includes/definitions/mibs/juniper.inc.php 13020 adama // JUNIPER-MIB::jnxOperatingDescr.9.1.0.0 = STRING: Routing Engine 0 13020 adama // JUNIPER-MIB::jnxOperatingDescr.9.2.0.0 = STRING: Routing Engine 1 13020 adama // JUNIPER-MIB::jnxOperatingState.9.1.0.0 = INTEGER: running(2) 13020 adama // JUNIPER-MIB::jnxOperatingState.9.2.0.0 = INTEGER: standby(7) 13020 adama // JUNIPER-MIB::jnxOperating1MinLoadAvg.9.1.0.0 = Gauge32: 123 13020 adama // JUNIPER-MIB::jnxOperating1MinLoadAvg.9.2.0.0 = Gauge32: 8 13020 adama // JUNIPER-MIB::jnxOperating5MinLoadAvg.9.1.0.0 = Gauge32: 56 13020 adama // JUNIPER-MIB::jnxOperating5MinLoadAvg.9.2.0.0 = Gauge32: 5 13020 adama // JUNIPER-MIB::jnxOperating15MinLoadAvg.9.1.0.0 = Gauge32: 27 13020 adama // JUNIPER-MIB::jnxOperating15MinLoadAvg.9.2.0.0 = Gauge32: 0 13020 adama $config['mibs'][$mib]['la'] = [ 13020 adama 'type' => 'table', // In table mode get first entry with test condition 13020 adama 'scale' => 0.01, 13020 adama // Walks 13020 adama 'oid_extra' => 'jnxOperatingState.9', 13020 adama 'oid_1min' => 'jnxOperating1MinLoadAvg.9', 13020 adama 'oid_5min' => 'jnxOperating5MinLoadAvg.9', 13020 adama 'oid_15min' => 'jnxOperating15MinLoadAvg.9', 13020 adama 'test' => [ 'field' => 'jnxOperatingState', 'operator' => 'eq', 'value' => 'running' ], 13020 adama ]; 13020 adama
I added unset($config['mibs'][$mib]['la']); // dave did this
This has fixed the problem, I don't need the la graph anyway. I had tried to add this to confg.php, but that didn't work.
I'm concerned that modifying the juniper.inc.php is not a good idea. Is there a better way to disable this?
