NeophyteNeophyteThanks - this would work, but it would hammer the API with the amount of datasources we would have per device...not to mention all the calls, and we are already doing a frequent amount of calls already.
Although in saying that, would you share the code you use within the datasource to update the property? My groovyscript is still a bit iffy.
NeophyteI don't think you would hammer the API because you don't run the API call unless the issue is detected. Right? Not every poll needs to employ API call. Only when exception is found that results in raising alert. I actually have a logic inside my script to fetch the property value at the beginning of poll and only update it if the issue is detected and the new property value needs to be output. Hopefully you don't run into too many alerts per device per DataSource per day, if you do, you create Alert fatigue and that's not good either.
As far as the script I use PowerShell as my choice of scripting language and I would have to scrub it in order to publish it. But there are tons of examples out there for both, groovy and PS on how to update API enpoints.
Lastly, I am again acknowledging, it would be nice if this capability was available out of the box. But since it is not, and based on business requirements, I have to do custom solution instead.