When I couldn’t get this to work I modified the way alerta sends alerts to InfluxDB to put them all in one measurement with the alert name as a tag (vs. multiple measurements w/each alert name its own measurement). That gave me some other benefits, so I sort of let this go and then deleted the excess data that demonstrated this.
I’ve turned the old method back on, but the issue hasn’t reappeared. I don’t think I have all the cardinality I did the last time, so it isn’t a perfect test (and I was thinking the high cardinality might be the issue since the restricted query worked).
So I don’t know if it was just the measurements I had before and not the new ones, if it was the cardinality, or if I just was confused. I did copy and paste the queries, so I would hope I got it correct, but you never know.
I’ll leave the parallel data flow in place for a while to try to build up some cardinality and post back if I can duplicate it. Thanks for the reply.
It’s certainly much easier to use which is why I switched it. The alerta-contrib InfluxDB plugin uses one measurement per alert name, so I think I’ll submit a pull request to at least give people the option.