Skip to content

Fix: Threshold comparison to only apply for ranged values #806

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.

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

Merged

Conversation

LordHepipud
Copy link
Collaborator

Fixes Icinga for Windows threshold comparison which wrongly compared warning/critical thresholds for non-range values (like Match)

Fixes #784

@LordHepipud LordHepipud self-assigned this Apr 22, 2025
@cla-bot cla-bot bot added the cla/signed label Apr 22, 2025
@LordHepipud LordHepipud added the Bug There is an issue present label Apr 22, 2025
@LordHepipud LordHepipud added this to the v1.13.3 milestone Apr 22, 2025
@LordHepipud LordHepipud merged commit fa7e729 into master Apr 22, 2025
1 check passed
@LordHepipud LordHepipud deleted the fix/threshold_comparison_for_non-range_arguments branch April 22, 2025 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug There is an issue present cla/signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

icinga-powershell-framework 1.13.2 - Heartbeat: Warning threshold range "13" is greater than Critical threshold range "6"
1 participant