Open for Voting
over 1 year ago

Custom Property Automated Rules

We have quite a few custom properties that get added, though quite a few of them could be automatically detected.

For example we have the following custom property

Region

-London

-New York

-Dubai

etc

All of which need to be manually selected, though this could be worked out using the same "Dynamic Query" that the groups uses and allocated automatically.

Region Default Value: London

Rule 1: IF hostname includes LON THEN Value: London

Rule 2: IF IP Address is part of 10.0.0.0/24 subnet THEN Value: Dubai

etc

This would greatly help enhance the Node Discovery Auto Import feature!

Parents Comment Children
  • HerrDoktor​ is correct, PeterLyttle. Let's break it down just a bit.

    If you alert is set up like this:

    Trigger Condition:

    All child conditions must be satisfied (AND)

    Node - Node Name - contains - JCMO -

    Trigger Actions:

    1. Change 'Address1' property to '100 W High St'

    2. Change 'AddressCity' property to 'Jefferson City'

    What will happen is that when the alert runs, it will trigger off of the name. The actions then happen. Since the trigger condition hasn't changed, the alert will not reset. Each time the alert runs, it will trigger and overwrite these properties.

    If you add a condition like so:

    Trigger Condition:

    All child conditions must be satisfied (AND)

    Node - Node Name - contains - JCMO -

    Nodes Custom Properties - Address1 - is empty

    Trigger Actions:

    1. Change 'Address1' property to '100 W High St'

    2. Change 'AddressCity' property to 'Jefferson City'

    The alert will trigger only if the node name has JCMO in it and the address is blank. Once triggered, the actions populate the address fields. This then cause the trigger condition to no longer be true, resetting the alert. The next time the alert runs, it will now skip this node as the address1 field will no longer be empty.

  • Yea that's the way I have it -

    Trigger Condition

    Node - Node Name - contains - LON

    Node Custom Properties - Site - is empty

    Meaning that it should reset after the trigger action populates the Site custom property.  I've been seeing a few strange things with names in NPM12 and already have a support case open.

  • We've worked out what was happening with the help of support.

    Basically as the Site is empty (NULL I guess) we had tweaked the query to be NOT EQUAL TO LON rather than the IS EMPTY

    Adding an OR condition block so the trigger read -

    Node - Node Name - Contains - LON

    AND

    (Node Custom Properties - Site - IS EMPTY OR Node Custom Properties - Site - NOT EQUAL to LON)

    This sorted it and also sorted out the reset trigger!