inadequate performance of alarms endpoint of v1 REST API
Description
The v1 alarms endpoint is not fast - in doing some tests it was taking at least ~5 seconds to respond to queries for alarms with specific reduction keys. I opened a support ticket and Alejandro Galue let me know about the as of yet undocumented v2 endpoint for alarms, which is effectively instant, so we're using that now, but thought it was worth making an issue.
The v1 alarms endpoint is not fast - in doing some tests it was taking at least ~5 seconds to respond to queries for alarms with specific reduction keys. I opened a support ticket and Alejandro Galue let me know about the as of yet undocumented v2 endpoint for alarms, which is effectively instant, so we're using that now, but thought it was worth making an issue.