...

OpFlow requires the same services as NMIS, plus:

• opflowd

Issues with Poll Interval

There is a problem the Poll Interval <30m set from the beginning to a Service and then modified to ≥30m.

Recreated problem

We recreated the problem in lab-primary1, using the SSH service of port22 with 1m, adding it to the node testnode3.

https://lab-primary1.opmantek.net/cgi-nmis9/network.pl?act=network_service_view&node=testnode3&refresh=180&widget=false&cluster_id=84e2260c-bb7b-487d-8b5c-c4e9ebc20a65

Image Removed

It is observed that the graphs start to show information, both in NMIS and in opCharts (from 15:35/15:40 to 15:55).

Image Removed

Image Removed

Then, the Poll Interval of the service is modified to 30m.

Image Removed

The rrd update is observed at 15:55.

Image Removed

After 30m, no graphing is observed in the configured Poll Interval, but the rrd update at 16:22 is observed.

Image Removed

Image Removed

Image Removed

We wait another 30m and the service continues without graphing, but we do see a new update in the rrd.

Image Removed

Image Removed

Image Removed

The Poll Interval of the service is set back to 1m (at 16:55).

Image Removed

Image Removed

The charts are recovering, but there is already a 1-hour gap.

Image Removed

Image Removed

New tests with a monitor with 30m from the beginning:

Image Removed

Image Removed

Image Removed

Image Removed

Image Removed

 Poll Interval is changed to 1h and continues to work fine:

Image Removed

Image Removed

Image Removed

Image Removed

Now with 5m:

Image Removed

Conclusion

If a Poll Interval of a service that is 1m, 2m, 10m, 15m is modified to 30m or more, the service graphs are stopped. If the Poll Interval is returned to the initial value (less than 30m), the graphs recover but a gap is observed at the time when it was 30m or more.

If a Poll Interval of a service that is 30m is modified to 60m, and then to 5m, the service graphs continue to work fine.