DataSources missing
Microsoft_SQLServer_AlwaysOnAvailabilityGroups is not showing under the devices.
It's visible in Settings-DataSource but not in Modules- LogicModules-My Toolbox or LM Exchange. It disappeared and no data is being collected.
lucjad
Posted 2 years ago·Last reply 2 years ago
6 comments
LM User
·2 years agoMike_Rodrigues
lucjad
OP2 years agoIt happened after the Microsoft_SQLServer_AlwaysOnAvailabilityGroups module update from version 2.7.0 to 2.9.0.
I was able to find the module in My Toolbox but it says it's installed but not in use.
It's visible under DataSources in Settings tab but is not displayed under the devices and no data is being collected. Also, Audit Logs say that instances were removed from availability groups at the same time the module update was done.
Was there a specific change between these versions that impacted the way the AGs should be configured?
With version 2.7.0 we had Node's system.categories set up with SQL properties (system.categories: MSSQL and mssql.sql_server_instances / MSSQLSERVER + url and jdbc of course) and Listener with these (system.categories: WSFC_Node,SQL_Node,WSFC_VNN,MSSQL and mssql.sql_server_instances / MSSQLSERVER and url/jdbc)- and it all worked before module update.
Also, Node and Listener were 2 separate devices in Logic Monitor.
Did it change after the module update??
LM User
·2 years agoI don't know if it changed, but if you can see it in settings or in the module toolbox, what happens when you test discovery (besides the infuriating lack of information helpful in troubleshooting)?
lucjad
OP2 years agoI attach screenshot- I tested active discovery on the listener device and got: No instance is discovered for the selected device during this test.
I got a message from LM Support Team saying that addCategory_WindowsFailoverCluster is not enabled. Would that be the cause of it?
Michael Rodrigues
·2 years agoIt looks like the update broke AD for you. It could be that you need the accompanying PS as support mentions, but AFAIK that should only be responsible for tagging the device. The fact that you ran AD manually and got nothing makes me think this needs to be escalated to the ME team for a fix. Do you still have an open ticket with support?
lucjad
OP2 years agoYes, I have the ticket still open.