Opened 2 years ago
Closed 6 months ago
#426 closed defect (fixed)
Perfdata Output checkMEM
| Reported by: | bertram | Owned by: | mickem |
|---|---|---|---|
| Priority: | 1 | Milestone: | 0.4.1 |
| Component: | CheckSystem | Version: | 0.3.9 |
| Severity: | Support Requests | Keywords: | |
| Cc: |
Description
Change History (4)
comment:1 Changed 23 months ago by dguenault
- Version 0.3.8 deleted
comment:2 Changed 23 months ago by mickem
Humm... I though the point of the unit was to allow applications to handle the unit... I would file this as a defect with centreon or whatever...
Nothing I will fix in the near future anyways (to much work, and would clobber the "option list" to much)..
Michael Medin
comment:3 Changed 15 months ago by mickem
- Milestone set to future
- Version set to 0.3.9
comment:4 Changed 6 months ago by mickem
- Milestone changed from future to 0.4.1
- Resolution set to fixed
- Status changed from new to closed
This has been resolved in last build.
There is an option to configure this:
* Added perf-unit to allow for stable performance data units (if not specified it will guess which is the current solution).
checkmem type=paged MaxWarn=80% perf-unit=M
=> 'paged bytes %'=34%;80;0 'paged bytes'=8454.04M;19629.84;0;0;24537.3
checkmem type=paged MaxWarn=80% perf-unit=K
=> 'paged bytes %'=34%;80;0 'paged bytes'=8655200K;20100963.19;0;0;25126204
checkmem type=paged MaxWarn=80% perf-unit=B
=> 'paged bytes %'=34%;80;0 'paged bytes'=8872108032B;20583386316;0;0;25729232896
checkmem type=paged MaxWarn=80%
=> 'paged bytes %'=34%;80;0 'paged bytes'=8.25G;19.1;0;0;23.96
Note: See
TracTickets for help on using
tickets.









Same problem here. This cause in Centreon graph to be crushed. Any way to choose MB or GB as the unit ? or not returning unit at all in performance data ?