Hi,I did a DataSource update the other day and it looks like the built-in SQL Server dashboard is now broken, because the updated DataSources now have one of these:hasCategory("MSSQL") && !hasCategory("SQL_Node")hasCategory("MSSQL") && !hasCategory("WSFC_VNN")I’m guessing the bold bit is new/changed because previously my SQL AG servers were shown in the built-in Dashboards and now they’re not. Only non AG SQL’s are shown.Is this intentional?Thanks

Hi, @ldoodle To answer your question, yes, the change was specific. We made that change to our SQL modules in 2020 in order to differentiate from SQL monitoring on Windows Server Failover Clusters, which have their own SQL modules. https://www.logicmonitor.com/support/monitoring/applications-databases/windows-server-failover-cluster-on-sql-server-monitoringKeep in mind these risks to updating a module are always present. We at LM Support often encourage updating, but the risks are there and it’s up to you to move with caution. Clone the current module before updating the Core as a precaution, or review the changes with a diff check.And because we love sharing our documentation, here’s an article on updating modules and the risks involved:https://www.logicmonitor.com/support/logicmodules/about-logicmodules/keeping-your-datasources-up-to-date#h-risks-to-updating

I’m not sure what that category (WSFC_VNN) is for, but the addition of that clause to the appliesto is probably to exclude some systems that are known not to work with that datasource. Does the datasource show data on the device level? Maybe some filtering in the dashboard widget needs to be updated.

LM generally (but not always) will summarize bigger modules changes in the next release notes. You can also check the “commit history” in the Exchange if they added any. In general I would try to review what specifically changed when upgrading DSes. Especially if AppliesTo changes as that might cause loss of historical data.

Ha, don’t need to guess - from the update log:update value=hasCategory("MSSQL") && !hasCategory("WSFC_VNN"), old value=hasCategory("MSSQL")I’m happy to remove that new clause in the DataSources if needed, but there must have been a reason for this change.

Licensing question: you consume a device license for every device your collectors talk to, not what they talk about. For example, you can monitor vCenter and talk about 1000 VMs managed by that vCenter, but you’re only consuming 1 license because you’re only talking to vCenter.

Forum Discussion

ldoodle

Advisor

3 months ago

SQL Server DataSources - Updates

Hi,

I did a DataSource update the other day and it looks like the built-in SQL Server dashboard is now broken, because the updated DataSources now have one of these:

hasCategory("MSSQL") && !hasCategory("SQL_Node")
hasCategory("MSSQL") && !hasCategory("WSFC_VNN")

I’m guessing the bold bit is new/changed because previously my SQL AG servers were shown in the built-in Dashboards and now they’re not. Only non AG SQL’s are shown.

Is this intentional?

Thanks

12 Replies

ldoodle
Advisor
3 months ago

Licensing question: you consume a device license for every device your collectors talk to, not what they talk about. For example, you can monitor vCenter and talk about 1000 VMs managed by that vCenter, but you’re only consuming 1 license because you’re only talking to vCenter.

Yeah I understood that - that vCenter example was major plus for us with choosing a monitoring product/platform.
But I wasn’t quite sure how it worked with a virtual thing like a cluster name, VIP, SQL AG listener etc.
ldoodle
Advisor
3 months ago
Thinking about it differently… I think based on what you said it would be 2 licenses:
a physical server getting polled on its OOB port (iDRAC, iLO etc.) AND Windows IP, that would be 2 rather than just 1.

Forum Discussion

SQL Server DataSources - Updates

12 Replies

Related Content

LogicModule Updates in UIV4

Plugin update for LogicMonitor to ServiceNow Integration

Bug early release Collector Update V34.500

vmWare vCenter Server - permissions

DataSource with PowerShell script

Recent Discussions

New VMware modules dropped

LogicMonitor - Mulesoft Integration(##EXTERNALTICKETID##)

SDTing via API, one source work the other does not

Customizing Alert Message for Integrations - Question.

Collectors: Open Telemetry vs. LM Collector