If you are doing large queries which touch a lot of timeseries you will need
lots of memory and CPU.
Ideally you would minimise such queries, or use pre-aggregated metrics (created
with recording rules) to simplify what is being requested.
I'd suggest looking at what you are try to achieve. Are
Can someone please help here
On Tuesday, May 19, 2020 at 2:25:01 AM UTC+5:30, Dinesh N wrote:
>
> Hi Team,
>
> I have been using Thanos-Prometheus stack and running into high
> cardinality issues where CPU goes till ~80% and then goes down and this
> happens when firing high cardinality queries
2 matches
Mail list logo
