Skip to content

Added service label cmk/mssql_recovery_type for mssql_backup services - #949

Open
lbuhleie wants to merge 1 commit into
Checkmk:masterfrom
svalabs:feature/mssql_backup_service_label_v2
Open

Added service label cmk/mssql_recovery_type for mssql_backup services#949
lbuhleie wants to merge 1 commit into
Checkmk:masterfrom
svalabs:feature/mssql_backup_service_label_v2

Conversation

@lbuhleie

Copy link
Copy Markdown
Contributor

General information

This changes the MSSQL Backup service discovery to also discover a service label, based on the recovery type of the SQL instance.

Proposed changes

Prior to this, the MSSQL Backup service would only discover the service. With this, there is a new service label being discovered for those services: "cmk/mssql_recovery_type":
image

This enables Checkmk administrators to easily set different thresholds for MSSQL backup services based on the recovery type. For example, Checkmk administrators can now create one rule that only matches on Instances with the recovery type SIMPLE, that disables thresholds for the Log backup.
Prior to this, such a rule would have to be set on each host and instance individually.

I already did a Pull Request for this (#909), but some Pipelines failed and I lost track of it. So this is the second attempt for this.

@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown

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.
Please take a look at the ‘Checks’ section for details on the test results and make the necessary changes.

This pull request will be closed due to inactivity after 60 days, if no action is taken.

@github-actions github-actions Bot added the Stale Scheduled for auto-close label Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Stale Scheduled for auto-close

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant