So, maybe I'm doing something wrong, but I don't think so.
The scenario is that we set custom properties on nodes using alerts. We set the custom property because it makes some other things easier to do, such as reporting. This is simple stuff like the building number, which we grok from the name of the device.
The problem is, a bunch of devices kept firing our alert over and over. In doing some research, all of them were unmanaged currently. So I put something in to check the status and if it wasn't up it wouldn't try.
But, that begs the point, why can't it do this? So, I went in to the Custom Property Manager, and was able to set the fields just fine, so its not like you can't do it.
But, I'm guessing that the "Trigger Action" that I set up to "Change a Custom Property" is somehow preventing this? I know the alert was triggering because I saw it in the Alert Manager.
Anyone else see this behavior?
I'd like to see this fixed...
