Our company recently upgraded from Influx v1.8.10 to v2.7.0.
Sometimes we have queries that eat up a lot of resources. I want to be able to identify and stop (if necessary) these queries.
In Influx v1.8.10 this could be done by executing “SHOW QUERIES” and “KILL QUERY ” in the influx CLI.
How could this be done in Influx v2.7.0?
Or are there other ways of managing resource hungry queries?
Hello @Sam_Donche_Clarebout,
You can use the flux profiler to evaluate specific queries:
Does that help?
Also cool to be aware of the following but kinda a tangent
