Werk #19249: MSSQL Transactions service linking to wrong check parameters rule
| Component | Checks & agents | ||||||
| Title | MSSQL Transactions service linking to wrong check parameters rule | ||||||
| Date | May 12, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Previously, clicking "Parameters of this service" on an MSSQL Transactions service would take you to the MSSQL locks rule - which configures lock request, timeout, deadlock, and wait thresholds. That rule has nothing to do with transactions.
The MSSQL Transactions check monitors transactions per second, write transactions per second, and tracked transactions per second. It now correctly links to its own dedicated rule MSSQL Transactions, where you can configure upper thresholds for each of those three counters.
No migration of existing rules is needed: the locks rule never had any effect on the transactions check because the two rulesets use entirely different parameter keys.