Fix: Map missing WARNING-state#933
Open
sva-mh wants to merge 2 commits into
Open
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
General information
Then SAP-Hana disk-usage-checks did not map the SAP-WARNING state to CMK-Warn.
As result SAP-WARN lead to a CRIT-Ticket. This lead to creation of non-necessary on-call tickets.
Bug reports
This was observed in CMK 2.3 already and the behaviour was not changed since then.
This available states delivered by the database-query are provided are documented here:
https://github.com/SAP-archive/sap-hana-cloud-hana-database/blob/main/docs/sql-ref/020-System-Views-Reference/022-Monitoring-Views/m-system-overview-system-view-20c61f0.md
Note: I did not change then "UNKNOWN"-mapping although it is not documented, since it does not harm
and may have been seen on other/older SAP-setups.