This is a usual case with big switch chassis. There is another solution is to just filter out a few ports, you can for example graph only uplink-ports or similar. And then you can make observium ignore the whole ifxEntry-table and only poll certain ports by activating the separate_walk-function on the device.
Would that maybe work for you? /Markus
Den mån 6 maj 2019 kl 16:54 skrev Steffen Klemer via observium < observium@observium.org>:
Hey list,
how much work would it be to have an option to adjust the rrd step size per device? Background is that we have a HP/H3C chassis that even with latest firmware takes average 1000s to poll; with fdb already disabled. 98% of the time is spent in the ports module, polling ifEntry and ifxEntry. We'd really like to at least get an hourly graph of the traffic which is better then nothing. The idea is to put this dev into its own group and have a different cron job for it (excluding this group from the default one).
We do have a case with HP that is open for 2 years so the 'tell the vendor that their SNMP engine is crap'-part was already done...
lg Steffen
-- Steffen Klemer E-Mail: steffen.klemer@gwdg.de Tel: +49 551 201 2170
GWDG - Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen Am Faßberg 11, 37077 Göttingen
Service-Hotline: Tel: +49 551 201-1523 E-Mail: support@gwdg.de
Kontakt: Tel: 0551 201-1510 Fax: 0551 201-2150 E-Mail: gwdg@gwdg.de WWW: https://www.gwdg.de
Geschäftsführer: Prof. Dr. Ramin Yahyapour Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger Sitz der Gesellschaft: Göttingen Registergericht: Göttingen, Handelsregister-Nr. B 598
Zertifiziert nach ISO 9001
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium