Update citrix_state.py - added vmtoolsstate config #784
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.
Thank you for your interest in contributing to Checkmk!
Consider looking into Readme regarding process details.
General information
When monitoring citrix terminalserver with the citrix instance state it can often occour that the vmtoolstate is unknown, in special after reboots. this produces currently a lot of unknown errors - so we need to whitelist this as the "issue" has no affect and the systems are fully functional - it's just an citrix issue.
Configuration of the registrationstate was possible, but vmtoolstate not.
States are:
"vmtoolsstate": {
"NotPresent": 2,
"Unknown": 3,
"NotStarted": 1,
"Running": 0,
},
Bug reports
no cmk bug
Proposed changes
Just add the functionality to configure the vmtoolsstate via wato rules.
What is the expected behavior?
configuration of vmtoolsstate
What is the observed behavior?
the outcome of vmtoolsstate is not configurable