Alerting with Custom Properties - Trigger Condition Yes/No

Version 6

    I wanted to outline some additional ways to help with cutting down on alert noise with Orion. I'm building off this previous thwack post.

     

    This post talks about using a Custom Property as a toggle on a per node basis. You can also create similar Custom Properties for Applications and Interfaces. The concept is the same.

     

    1. First, i created a Custom Property (Settings > Manage Custom Properties) and I called it 'SendAlertNode.' You can call it whatever you prefer but that is the name that I'll be using for this article. The format is Yes/No.

    2.png

     

    2. You can then add this Custom Property in the Trigger Condition of an alert. You can use any existing alerts or duplicate them if needed. Once you edit the alert you'll need to go to the trigger condition section. In the "Scope of alert" section, click the green plus sign and add a 'Single Value Comparison (Recommended).' Then browse for the name of the Custom Property, SendAlertNode. Set the value 'is equal to' 'Yes.'

    2016-09-08 09_05_12-Edit Alert - _ SMS_Slack Alert me when a Node has an issue (custom)_.png

     

    By adding this condition a node needs to have that Custom Property set to yes to ever see an alert for it. I used this to separate my critical nodes from non-critical nodes.

     

    Here is another article I created around using Custom Properties with alerting.

    Alerting with Custom Properties - Trigger Action - Default Email

     

    Here is an article that outline how you can modify a Custom Property via Orion's API's.

    PowerShell script to modify a NODE Custom Property via Rest API/JSON

     

    If this was helpful, feel free to rate this article.