Forum Discussion

Cole_McDonald's avatar
Cole_McDonald
Icon for Professor rankProfessor
2 months ago

Did Property Evaluation change in UIv4?

To bulk change things for a class of server (in this case, 2008 Servers), I used to be able to make a dynamic group in "Device By Type" to set a property on all devices.

I use this to determine whether or not a device should create a ticket through rule>escalation>integration based on our contracts.

I just added 2008 servers to our monitoring, I want the data from them, but we don't have them generate tickets as they're EOL... but can cause environmental issues that would take longer to find causes for if we don't have the data.

They show up in the "DBT/Windows EOL" group, but the company.response="none" property set there isn't applying.  It's inheriting the one from it primary containing folder/group instead.  Everything else in that primary folder should apply a value of "standard" so I have that set as we bring on a client's environment and shift them from on-boarding to production support.

My concern is that changes to classes of servers will now inherit incorrectly.  Not just properties, but potentially differential SDTs, Alert Thresholds, etc.

3 Replies

  • jhupka's avatar
    jhupka
    Icon for Neophyte rankNeophyte
    2 months ago

    If the DBT/Windows EOL group is only two-deep, and that property is being set somewhere else that is three or more levels deep, then LM will pick the deepest property to apply (it is assuming deeper in the resource tree=more specific)

    • Cole_McDonald's avatar
      Cole_McDonald
      Icon for Professor rankProfessor
      2 months ago

      That was my fear... makes it hard to differentiate common types of devices across a broad set of groups to make them change a common prop/threshold.

      I'd thought it worked backwards from the device up until it found a setting.  I know from other pieces that evaluations in some cases are alphabetical rather than by index/ID (Object Creation order).  I may test with a group alphabetically sooner than "Clients/" to see if it changes the behavior.

      • jhupka's avatar
        jhupka
        Icon for Neophyte rankNeophyte
        2 months ago

        I haven't had to create any dummy resource folders (yet) to force a particular depth, but I figured this type of conflict came up in our environment then I would just come up with some naming standard that is obvious that is what the folder is for, like "LM_Force_Depth" or something like that.

        The good news to me is that there's consistent rule for this one so we can fudge it if necessary with a minor workaround like this.