none
scom 2012 Exclude SQL2016 object from a computer group

    Pregunta

  • Hi, we have SCOM2012 installed and we have a group of windows machine called critical. In this group we have different server with different Os and all is working good. Now we want to receive all alert for these server EXCEPT those related to SQL which are sent to a different team so we added all version of MSSQL.. and that was working good untill a few months ago when we added an SQL2016 enterprise server and we proceeded the same way to add the new MSSQL into the exclusion but for an obscure reason we still receive all the SQL related alert, since these alert are sent to the "standby phone" 24/7 we really don't want to receive stuff we are not responsible for and this is really annoying that the exclusion that were working (up to SQL 2014) are not working for the new SQL2016. here are screenshot of the group and exclusion we have in place and we keep receiving SQL related alert so I'm out of idea and would appreciate suggestion.

    SCOM 2012 Service Pack 1 version: 7.0.9538.1136

    SQL2016 MP version is: 6.7.20

    Group member:

    https://imgur.com/0c7VyHn

    Exclusion list capture:

    https://imgur.com/UKUWwrx

    https://imgur.com/faJOCs8

    https://imgur.com/oqEDYoC




    viernes, 10 de noviembre de 2017 21:22

Respuestas

  • To fix the problem, we finally removed everything but the SCOM agent from the group membership and manually added stuff we really want to be alerted on in the group.
    • Marcado como respuesta Cividan miércoles, 13 de junio de 2018 16:09
    miércoles, 13 de junio de 2018 16:09

Todas las respuestas

  • Hi,

    Are you getting notifications for all your SQL versions or just 16? You can exclude the SQL database class instances from your group membership criteria in the XML of the MP.

    Please see this for reference:

    https://social.technet.microsoft.com/Forums/en-US/81ca3e61-a2aa-4354-b65e-0bc9f10451b3/how-to-create-group-of-all-nondc-servers?forum=operationsmanagerauthoring

    Hope this helps,

    Sam

    • Propuesto como respuesta GouravIN lunes, 13 de noviembre de 2017 4:47
    • Votado como útil Cividan lunes, 13 de noviembre de 2017 15:40
    domingo, 12 de noviembre de 2017 6:43
  • >> we want to receive all alert for these server EXCEPT those related to SQL which are sent to a different team
    1) What is your notification subscriptions ctrieria?
    2) View group membership to check whether it exclude all SQL 2016 related objects
    3) view problematic SQL alert related alert and check its source. Is this source came from  SQL 2016 related object which you exclude foem your group membership?
    Roger
    lunes, 13 de noviembre de 2017 2:24
  • As Sam , Suggested to avoid those irrelevant alert notification you can exclude the SQL database class or you can also add server only and application, services via using object tab.

    Thanks, Gourav

    lunes, 13 de noviembre de 2017 4:51
  • >> we want to receive all alert for these server EXCEPT those related to SQL which are sent to a different team
    1) What is your notification subscriptions ctrieria?
    2) View group membership to check whether it exclude all SQL 2016 related objects
    3) view problematic SQL alert related alert and check its source. Is this source came from  SQL 2016 related object which you exclude foem your group membership?
    Roger

    Hi,

    #1 - notification criteria are based on membership of the critical server group

    #2 - Group membership doesn't show the MSSQL object

    #3 - Alert are originated from: MSSQL 2016 even tho the MSSQL2016 is excluded from the membership and not displayed when I show group membership, see capture below:

    https://imgur.com/TRQwM1o



    • Editado Cividan lunes, 13 de noviembre de 2017 16:31 Typo
    lunes, 13 de noviembre de 2017 15:30
  • Hi,

    Are you getting notifications for all your SQL versions or just 16? You can exclude the SQL database class instances from your group membership criteria in the XML of the MP.

    Please see this for reference:

    https://social.technet.microsoft.com/Forums/en-US/81ca3e61-a2aa-4354-b65e-0bc9f10451b3/how-to-create-group-of-all-nondc-servers?forum=operationsmanagerauthoring

    Hope this helps,

    Sam

    Hi, this link explain how to exclude of a group but as I stated in my original question the SQL instance are already excluded. We are getting notification only from the SQL2016 all other SQL alert are not beeing sent, only those sent by SQL2016. See screenshot below for the suscription.

    https://imgur.com/qi2FK7o

    lunes, 13 de noviembre de 2017 15:40
  • Hello,

    I've observed sometimes exclusions in GUI don't work. But you can be absolutely sure when you make changes in the MP.

    Did you restart your subscription after adding sql 16?

    From console please try this:

    - Disable the subscription

    - Create a new group same as your current group, including all sql versions. (I'm assuming you've only added sql 16 to existing group)

    - Enable the subscription according to your criteria

    See if this helps

    Sam


    • Editado Sameer Mhaisekar lunes, 13 de noviembre de 2017 17:33
    • Propuesto como respuesta GouravIN martes, 14 de noviembre de 2017 3:12
    • Votado como útil Cividan martes, 14 de noviembre de 2017 16:45
    lunes, 13 de noviembre de 2017 17:31
  • Thanks, I will disable the subscription and re-enable it. How do you update the exclusion by editing the MP? I always did my exclusion from the GUI...
    lunes, 13 de noviembre de 2017 19:14
  • Hello,

    This will make more sense if you're a bit familiar with MP Authoring, or XML in general.

    To edit an MP in XML:

    1. Export the MP where you've created the group (Don't give any exclusion criteria). It will create a .xml file.

    2. Open the file in your preferred editor (or simple notepad)

    3. Find the group you've created, and edit in the membership criteria. In general it looks like this:

    <Membership>
    <Expression>
        <NotContains>
           <MonitoringClass>Your Exclusion criteria here</MonitoringClass>
        </NotContains>
      </Expression>
    </Membership>  

    4. Save the changes and import the MP back.

    However in your case if you say you can actually see the excluded objects aren't part of group members so this shouldn't be needed.

    Lets see if re-enabling the subscription solves your case.

    Thanks

    Sam

    martes, 14 de noviembre de 2017 10:22
  • To fix the problem, we finally removed everything but the SCOM agent from the group membership and manually added stuff we really want to be alerted on in the group.
    • Marcado como respuesta Cividan miércoles, 13 de junio de 2018 16:09
    miércoles, 13 de junio de 2018 16:09