Hiding of cache information in summary for local checks and MRPEs - #954
Hiding of cache information in summary for local checks and MRPEs#954Nipa0 wants to merge 1 commit into
Conversation
…& MRPEs \n\n Add service montoring rules for cached local and MRPE checks that enable the user to toggle whether the caching information is visible in the summary and the details or only the details.
|
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. Dein Vor- und Nachname seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. |
|
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
|
recheck |
|
Thank you for your contribution. This pull request has been marked as stale as it has not passed the automated tests and there was no activity for the last 14 days. This pull request will be closed due to inactivity after 60 days, if no action is taken. |
Add service montoring rules for cached local and MRPE checks that enable the user to toggle whether the caching information is visible in the summary and the details or only the details.
--
The representation of the caching information (Cache generated....) in the summary used to make it more difficult to read the actual summary information when looking at the service list, and is for most of our use cases superfluous. I therefore built in the option to disable this representation and replace the whole cache information in the summary with ◷ to indicate it is a cached monitoring keeping the actual caching information only in the details and making the representation more readable.
To be coherent I added this option for both local checks and MRPEs as the processing of cached checks is nearly identical, and the MRPE source code explicitely stated it was written in a manner to be coherent with the local checks.
I am not sure if the way I created the setting options is the best practice way and appreciate feedback on that.