Ticket #151 (closed enhancement: fixed)

Opened 4 years ago

Last modified 6 months ago

Perfcounter reported in scientific notation

Reported by: aaron@… Owned by: mickem
Priority: 1 Milestone: 0.3.4
Component: CheckSystem Version: 0.3.1
Severity: Feature Requests Keywords: CheckCounter
Cc:

Description

I'm monitoring a Windows Performance Counter that's an actual counter, not a gauge. So I need to compare its value to a previous one, so I can find out how fast it's changing.

Problem is, when I ask for it using CheckCounter, I get back a number in scientific notation, e.g. "2.53904e+006", rather than as an integer. And as you can see, I'm losing the last digit of the counter.

Is it possible to change the string formatting to integer rather than float or scientific notation? Or maybe format it wide enough to show the whole number for 32-bit (or even 64-bit) counters?

Change History

comment:1 Changed 4 years ago by mickem

  • Status changed from new to assigned
  • Type changed from defect to enhancement
  • Severity changed from Bugs to Feature Requests

possibly... might add a "syntax" or some such...

I am assumeing you are using NRPE right? (check_nt I think cant)

MickeM

comment:2 Changed 4 years ago by david.may@…

Hello, I have found the same problem. I believe this is actually a BUG (and not an enhancement) because the Nagios Plugin Development Guidelines, section 2.6 "Performance Data", item 8 states:

  1. value, min and max in class [-0-9.]. Must all be the same UOM.

I would interpret this to mean that only signed integer and decimal fractions are allowed as values.

comment:3 Changed 3 years ago by mickem

  • Status changed from assigned to closed
  • Resolution set to fixed
  • Milestone changed from 0.4.0 to 0.3.4

Fixed in the next RC (RC-3 out in a bit), grab it and let me know...

MickeM

comment:4 Changed 6 months ago by fhd

The default format in version 0.38 is still scientific notation, and I couldn't find a way to change that. Nothing here: http://www.nsclient.org/nscp/wiki/CheckCounter

Did I miss something?

Note: See TracTickets for help on using tickets.