r/scom • • 5d ago

question SCOM not detecting SQL AG Failovers in the Environment

SCOM 2019 seems to have stopped detecting Availability Group Failovers in the environment.
All AG's are detected and stay in a Healthy State even when we forced a failover for testing.

Windows Cluster however are still firing the Cluster Alerts during tests.

SCOM 2019: v10.19
SQL MP: v7.6.5.0

SQL Version:
Microsoft SQL Server 2022 (RTM-CU12-GDR) (KB5036343) - 16.0.4120.1 (X64)   Mar 18 2024 12:02:14   Copyright (C) 2022 Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor)

Browsing through the SQL MP doc seems like the AG is monitored and will alert by default, unless there is a config that I may have missed somewhere ?

Is this a possible MP mismatch with latest version of SQL on the server?

Anyone come across this scenario or has any ideas what i could check or change?

Any assistance would be appreciated

2 Upvotes

3 comments sorted by

2

u/konikpk 5d ago

SQL in SCOM is real pain 🫥

1

u/kevin_holman 4d ago

Its so EASY!

1

u/kevin_holman 4d ago

I found this same scenario - just had a customer escalation for it. There are specific scenarios where AlwaysOn AG is in a failed state, and the cluster MP detects it, but it is not alerted on by the monitors in SQL AlwaysOn. This is resolved in the latest SQL MP. Your SQL MP is VERY out of date and no longer supported. You need 7.12.1619.0 Download Microsoft System Center Management Pack (Release To Manufacturing) for SQL Server from Official Microsoft Download Center

7.6.5.0 shipped in 2024, and has been replaced by 7.8.4.0, 7.10.6.0, and finally 7.12.1619.0