2 Replies Latest reply on Sep 12, 2017 3:20 PM by Leon Adato

    Custom Properties

    bootneck1111

      I have a request from a client that is asking how they can manage Nodes during Maintenance Windows and eliminate Alerts for the duration period.

       

      Would I create a Custom Property to group the batch of Nodes together and then assign the Custom Property Group to the Trigger Condition of an Alert with An exclusion set against the Time & Day?

       

      What is the best practise of doing this as I'm guessing this is fairly common in view of Maintenance Upgrades/WSUS, and such like.

       

      My example scenario: I have Customer 1 who would like to run Windows Updates against all of their Server 2008 Nodes.

       

       

      Another question; I've been tasked to review the customers entire environment and their grouping doesn't seem to be logical enough for assigning the correct Alerts easily. I would like to better group their environment and have started at the Network Layer grouping together ALL Network Devices (Switches/Routers/Network Mgmt) via Custom Properties, and will then create Interface or other related Alerts and adding the Custom Property (Network Device Group) to the 'Trigger Condition' of the Alert. Is the a logical approach, or not?

       

      With the above in mind I have sub divided their environment up into Network, Physical Device, Virtual Hosts, Core Services, and Applications Layers. I have then placed all of the devices, servers, services, systems, and key applications into these (Custom Property Groups), and will assing these Properties to the required groups.

       

      In advance thank you for your advice and help.

        • Re: Custom Properties
          chad.every

          You're on the same track that I follow when carving out alerts. I've used this in the past for changing custom properties for alerting purposes.

          Alerting with Custom Properties - Trigger Condition Yes/No

           

          However, within the API you can now mute alerts which is the better route to go. I haven't got around to scripting that yet but I know there have been some posts out there about it.

          2 of 2 people found this helpful
          • Re: Custom Properties
            Leon Adato

            Agreeing with chad.every - back in the day (boy, don't *I* sound old?) we'd use a custom (boolean y/n) property called "mute", and all alerts would have to include a "If mute = n" check. But recently with the addition of the new, improved "mute" feature, you can do it all within the system.

             

            You still may need to group your nodes so you can get them all in the same place, but once you have that, you can use the ManageNodes page to mute them all in one fell swoop.

            2 of 2 people found this helpful