Hi,
I can see this one one of my graphs too, so I think this was a bug.
Migrating the collection to a newer format seemed to make it go away.
It should be fixed in r10122.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Aaron Finney via observium Sent: 13 October 2019 10:14 To: Observium Network Observation System observium@observium.org Cc: Aaron Finney aaron.finney@openx.com Subject: [Observium] Strange poller/graph behavior with Palo Alto
Heya Adam et al,
I'm trying to help the corp side of the house monitor a handful of Palo Alto firewalls (3220s/850s) using Observium, and am seeing the gptunnels and sessions graphs being alternately added/deleted each run. Example:
##### firewall.spaghetti.foo.baz [55] completed poller modules at 2019-10-13 09:07:03 ##### o Graphs [checked] availability, ping, ping_snmp, uptime, fanspeed, temperature, processor, mempool, storage, bits, hr_users, poller_perf, pollersnmp_count,pollersnmp_times, pollersnmp_errors_count, pollersnmp_errors_times, pollerdb_count, pollerdb_times,pollermemory_perf o Graphs [added] panos_sessions, panos_gptunnels o Poller time 5.6106 seconds o Updated Data uptime, last_polled, last_polled_timetaken, device_state
and the very next run:
##### firewall.spaghetti.foo.baz [55] completed poller modules at 2019-10-13 09:07:31 ##### o Graphs [deleted] panos_sessions, panos_gptunnels o Graphs [checked] availability, ping, ping_snmp, uptime, fanspeed, temperature, processor, mempool, storage, bits, hr_users, poller_perf, pollersnmp_count,pollersnmp_times, pollersnmp_errors_count, pollersnmp_errors_times, pollerdb_count, pollerdb_times,pollermemory_perf o Poller time 5.6037 seconds o Updated Data uptime, last_polled, last_polled_timetaken, device_state
This pattern repeats ad inifitum - any ideas?
Aaron