Added option to not discover MSSQL jobs with disabled scheduler - #948
Open
lbuhleie wants to merge 1 commit into
Open
Added option to not discover MSSQL jobs with disabled scheduler#948lbuhleie wants to merge 1 commit into
lbuhleie wants to merge 1 commit into
Conversation
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
1 participant
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
This introduces a new discovery rule that enables Checkmk administrators to deactivate the discovery of disabled mssql jobs.
Proposed changes
Until now, Checkmk tries to discover all MSSQL jobs. But this is often not wanted, as there can be old / unused jobs where the scheduler is disabled. Until now the only option was to manually disable those services. So with this PR there comes a new discovery rule, that makes it possible to not discover those disabled jobs:
The default behaviour of the discovery stays unchanged, this new rule is completely optional.
I already did a Pull Request for this (#910), but some Pipelines failed and I lost track of it. So this is the second attempt for this.