Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #8174] Availability function doesn't treat warning states as non-issue #71

Open
icinga-migration opened this issue Jan 8, 2015 · 3 comments
Open

[dev.icinga.com #8174] Availability function doesn't treat warning states as non-issue #71

icinga-migration opened this issue Jan 8, 2015 · 3 comments
Labels
bug High
Milestone
Backlog

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8174

Created by tgelf on 2015-01-08 15:51:19 +00:00

Assignee: mfriedrich
Status: Assigned
Target Version: Backlog
Last Update: 2015-09-21 20:30:50 +00:00 (in Redmine)

Icinga Version: 1.11.3
DB Type: MySQL
DB Version: 1.11.3
Jasper Version: 5.0.0

Warnings should NOT influence availability, I'm wondering whether nobody got aware of this glitch 'til now. Please find a working patch attached to this issue.

Cheers,
Thomas

Attachments
@icinga-migration
Copy link
Author

Updated by tgelf on 2015-01-08 15:52:33 +00:00

NB: Please note that the patch is against support/1.10 as the master is in an undefined state right now

@icinga-migration
Copy link
Author

Updated by berk on 2015-05-18 12:18:15 +00:00

  • Target Version set to Backlog

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-09-21 20:30:50 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich

@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@dnsmichi dnsmichi removed their assignment Sep 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug High
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@dnsmichi @icinga-migration