Cisco Temp Tracking
Hi Team,
We are looking for better tracking/alerting for temp increases overtime. We tried dynamic thresholds, but nothing worked out correctly in the sandbox. It was not accurate and caused ...
Forum Discussion
Agreed. It's not optimal. However, it is how I would build it were I requested to build it. I was asked to build something similar when a customer wanted to see the same instance's datapoint for the same time of day but one week earlier. The right answer is to use the alert clear interval.
I'm working internally to get the product team to build simple LM_API_GET functions into the groovy libraries so that we can just ask for data simply by doing "lm_api_get('device/devices')" or "lm_api_get('alert/alerts')" and just get back the data in a map. Ideally, it would preclude needing to create API tokens (since the collector already has access through the front door) and would also avoid all error handling related to authentication and http status codes.
