There’s currently work being done on
redoing memory pools to ‘definitions’ – probably related.
Maarten
From: observium
<observium-bounces@observium.org> on behalf of
Robert Williams <Robert@CustodianDC.com>
Reply-To: Observium Public Support
<observium@observium.org>
Date: Tuesday, February 21, 2017 at 10:20 AM
To: "Observium Network Observation System
(observium@observium.org)" <observium@observium.org>
Subject: [Observium] ASR9k RAM Changes
Hi,
Have there just been
some changes to the ASR9k RAM detection? Suddenly after
the overnight svn up we are seeing this for all 9k
chassis:
These 3 new items
are in alarm. The “reserved” and “image” are filtered
from all other devices by existing config.php – but
obviously no brackets on these ones.
$config['ignore_mempool_string'][]
= '(reserved)';
$config['ignore_mempool_string'][]
= '(image)';
However, the
‘processor’ one is actually wrong as it seems to be
using the CPU0 usage but a strange maximum of 3.81GB
instead of 7.81GB. I can’t filter this out because it
will drop all ‘processor’ types.
I remember something
historic relating to this where the maximums were
showing as around 4GB even though there is 8GB installed
and someone (Adam?) found and sorted it. This may or may
not be related though.
Cheers!
Robert
Williams
Custodian Data Centre
Email: Robert@CustodianDC.com
http://www.CustodianDC.com
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium