Alert for datasource instance datapoints based on Instance Description. Currently we cannot create an alert for datasource instance based on Instance description.
This is critical requirement for us.
Forum Discussion
Ok, if you are manually updating the description after discovery, then you'd have to replicate the work of updating the description in both datasources. However, since the same number of instances would be split over the two datasources, there wouldn't be any additional work. You'd just be doing it in a different place. Can I ask why you are updating the description after discovery and not doing it as part of discovery? I'm beginning to think the solution to your problem may be rooted in a fixation on the instance discovery. You may be able to accomplish your goal, whatever that might be, by manually (or preferably automatically) tagging the instances in a different way.
That said, take a look at this documentation: https://www.logicmonitor.com/support/logicmodules/datasources/datapoints/complex-datapoints#:~:text=Returns NaN-,Groovy Complex Datapoints,-Groovy complex datapoints
This bit may be particularly interesting: https://www.logicmonitor.com/support/logicmodules/datasources/datapoints/complex-datapoints#:~:text=instanceProps.get("auto.PropertyName")
