Radial Gauge Maximum Value (Only 32-bit)

Hello,

Since most of the firewalls and their interfaces are receiving and processing a lot of data, their counter sizes are also increasing. A lot of our firewalls right now have more 8G of RAM and I am trying to monitor the used value right now using NPM. However as far as I understand even though "Enable 64-bit counters" box is checked on the node page I am not able to set the maximum value for this counter more than 2.1 G. You can see the screenshots below. Is there a way to make the radial gauges use 64-bit display?

Find more posts tagged with

64-bit_counters

npm 11.5.2

counter

radial gauge

32-bit counters

Accepted answers

All comments

emregonen

Does no one have an idea?

silverbacksays

In the screenshot, the gauge is showing 3.27GB, which is larger than the 2.14, which is the largest integer (moving the decimal place). It appears you are seeing actual usage here, rather than limited by the counter. Assuming the custom poller value the gauge is looking at is looking at the correct OID.

emregonen

The OID is correct and the shown vaule is also correct. There is no problem with the counters. The problem is regarding the representation of the data.

When configuring a radial gauge it requests a minimum and a maximum value. This is the real problem the maximum value can only go up as high as 2,1 GB and not anymore. That's why even though the value is correct and 3,27 GB, the needle is all the way at the bottom and not somewhere in between. What should be done is to increase what I assume a 31 bit counter on the gauge.