none
Need to disable SQL Monitoring on the couple of servers monitored in SCOM RRS feed

  • Question

  • Hi All,

    I got a requirement that i need to disable sql monitoring for couple of the sql servers monitored in scom.

    As there are so many rules and monitors related to SQL, its not possible to do override on each one of them.

    Is it any method in scom, by which we can disable all sql monitoring for some servers?

    Please help!!


    AD

    Monday, October 21, 2019 10:58 AM

All replies

  • Hi,

    You can do the procedure below:

    1. Create a group.

    2. Add the servers that are hosting the SQL Servers that you don't want to be monitored to the group.

    3. Create an override for the discovery of the "SQL Server <version> Installation Seed" and target the group that you created.

    4. Then run the Remove-SCOMDisabledClassInstance after creating the override for the SQL Server discovery.

    You'll also find some guides over here:

    Disable SQL discovery for a group

    Disable Discovery of a SQL Server

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 21, 2019 11:58 AM
  • HI Leon,

    Thanks a lot for the detailed steps.

    Just one question, is it necessary to perform step 4?

    Performing till steps 3 of override is not enough?



    AD

    Tuesday, October 22, 2019 4:17 AM
  • Step 4 is a must.
    it is because override sql discovery does not automatic remove existing SQl entity. You must explicit remove its otherwise the sql monitoring still exist.

    Roger
    Tuesday, October 22, 2019 4:28 AM
  • Yes you do, as Roger said you will have to perform the Remove-SCOMDisabledClassInstance or the SQL Servers that you don’t want to monitor will still exist.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, October 22, 2019 5:15 AM
  • Hi leon,

    Just one question, we need to override the discovery of installation seed or db engine?

    and also override, when we run the "Remove-SCOMDisabledClassInstance", then how it will recognize that this command is only applied for the required servers?. Please make me understand this.

    Thanks & Regards

    Arpita Dhawan


    AD


    • Edited by AD_SC Monday, October 28, 2019 7:28 AM
    Monday, October 28, 2019 7:10 AM
  • Do you want to disable the monitoring for a specific instance or all instances on a server?

    The Remove-SCOMDisabledClassInstance will prompt you with a warning stating that it is a database-heavy operation (and it actually is). If you choose to continue, SCOM will effectively scrub all objects and relationships that have disabled discoveries


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Monday, October 28, 2019 7:33 AM
    Monday, October 28, 2019 7:21 AM
  • 1.Do you want to disable the monitoring for a specific instance or all instances on a server?-  i want to disable the sql monitoring for all instances of few sql servers.

    2. The Remove-SCOMDisabledClassInstance will prompt you with a warning stating that it is a database-heavy operation (and it actually is). If you choose to continue, SCOM will effectively scrub all objects and relationships that have disabled discoveries --  but i want to only remove for few sql servers not all


    AD

    Monday, October 28, 2019 7:55 AM
  • You can disable the discovery of the following:

    • MSSQL 20XX: Discover SQL Server 20XX DB Installation Source (seed)

    This discovery rule discovers a seed for Microsoft SQL Server 20XX installation. This object indicates that the particular server computer contains Microsoft SQL Server 20XX installation.

    Unfortunately you cannot alter the Remove-SCOMDisabledClassInstance cmdlet.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 28, 2019 8:19 AM
  • Just one question, we need to override the discovery of installation seed or db engine?

    1) You just to override the discovery the installation seed for particular SQl server.
    2) The DB engine is target on installation seed. As a result, db engine will not discovered when installation seed is not discovered.
    3) "Remove-SCOMDisabledClassInstance": deletes class instances for which you previously disabled discovery. The cmdlet also deletes all relationships that involve these class instances.



    Roger
    Monday, October 28, 2019 8:34 AM
  • So please suggest what i can do to disable sql monitoring for the particular servers, so you said running "Remove-SCOMDisabledClassInstance" command will remove all the disabled instances for all the servers, but i want it for only few servers.

    AD

    Monday, October 28, 2019 8:54 AM
  • Thanks Roger, So if i dont want to remove previously disabled discovery , then its not necessary to run this ""Remove-SCOMDisabledClassInstance"???

    because as of now, my requirement is to only disable the sql monitoring of few SQL servers


    AD

    Monday, October 28, 2019 9:00 AM
  • There are many things monitored in the SQL Server management pack, so disabling one or two monitors isn't going to stop all the other alerts from being generated.

    This is the reason why you want to create an override for the discovery of this server for SQL, the seed discovery that starts the initial SQL discovery, and to remove the disabled discovery the Remove-SCOMDisabledClassInstance command must be run.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 28, 2019 9:10 AM
  • but this command will remove all sql discovery for all disabled instance right?, that i dont want to do.


    AD

    Monday, October 28, 2019 9:41 AM
  • Then you will have to create a group of the servers that contain the SQL Servers that you do not want to monitor, then create overrides for every specific monitor and target the group.

    You'll find all the different SQL Server discoveries/monitors here:
    https://systemcenter.wiki/?GetCategory=SQL+Server


    Blog: https://thesystemcenterblog.com LinkedIn:

    Monday, October 28, 2019 9:45 AM
  • >>but this command will remove all sql discovery for all disabled instance right?, that i dont want to do.

    In other word, you want to retain the discovery instance but disabled its monitoring without one by one override its monitoring. Thsi is not possible.



    Roger
    Monday, October 28, 2019 9:49 AM