Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Enhancement Request] Perfdata Total size of Aggregates and Volumes #82

Open
MarcusCaepio opened this issue Jan 22, 2019 · 0 comments
Open

[Enhancement Request] Perfdata Total size of Aggregates and Volumes #82

MarcusCaepio opened this issue Jan 22, 2019 · 0 comments
Labels
enhancement help wanted

Comments

@MarcusCaepio
Copy link

MarcusCaepio commented Jan 22, 2019 •
edited
Loading

check_netapp_ontap version: v3.01.171611
Monitoring solution: Icinga2 + InfluxDB/Grafana

Hi all,
Currently the perfdata metrics are *_used and *_free. An additional _totalsize would be nice.
Also the warning and critical thresholds in the perfdata would be nice

Regards,
Marcus
Elias481 added a commit to Elias481/check_netapp_ontap that referenced this issue Jul 20, 2020
@Elias481
fix performance data output on space monitors (entities at critical w…
d1a3dbf 
…here skipped)

* this is just a least-instrusive fix for this impornat issue (fixes district09#74)

from my point of view the thing should be restructered further:
* call space_threshold_helper just once with both thresholds
* use a threshold-check function for the recurring task to determine intAlertLevel for a condition result
* include  thresholds in perf-data (also requested in district09#82) which would be quite hacky currently and I did not do yet despite I also want it
* output perfdata also for metrics where no threshold is defined (threshold is for alerting but a historical graph would be fine even if no alert is defined)
Elias481 added a commit to Elias481/check_netapp_ontap that referenced this issue Sep 24, 2020
@Elias481
fix performance data output on space monitors (entities at critical w…
7e6d5c1 
…here skipped)

* this is just a least-instrusive fix for this impornat issue (fixes district09#74)

from my point of view the thing should be restructered further:
* call space_threshold_helper just once with both thresholds
* use a threshold-check function for the recurring task to determine intAlertLevel for a condition result
* include  thresholds in perf-data (also requested in district09#82) which would be quite hacky currently and I did not do yet despite I also want it
* output perfdata also for metrics where no threshold is defined (threshold is for alerting but a historical graph would be fine even if no alert is defined)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@willemdh @MarcusCaepio