Thanks very much, Mike.
> I generally don't like to have LM DataSources attempt to communicate back to LM itself, I personally find it a bit hacky and avoid it unless there isn't another solution.
Agreed. It feels icky to me too.
> Try looking at Complex DataPoints rather then have a DataSources that attempts to re-process it's own data.
My impression is that complex data points cannot go back in time to look at older samples. If that's true, then I don't think they will meet my needs in this instance. The alert logic needs to look at the last hour of history and make decisions based on statistics/trends over that hour. Is there any way to do that without using the REST API?
> I'm not sure you can use python or other languages in DataSources, or you would atleast need to install those langueses on all your collectors.
Yes. I ran into problems trying to use Python for external script data collection shortly after sending my first message.
> There is a section of the LM APIv1 docs with different language examples at https://www.logicmonitor.com/support/rest-api-developers-guide/v1/rest-api-v1-examples, you will also find various examples in the community and on Mike Suding's Blog (this is a great resource).
Awesome. That's just what I was looking for.
I'll tinker around with doing it in Groovy, but I'm still hoping there's a better way which doesn't require LM communicating with itself with the REST API.
Here are some alternatives for which I've searched, but could not find:
1.) Complex data points being able to access older samples.
2.) Complex trigger expressions which support logic such as min/max over certain time ranges.
Thanks again.
