Srikanth Chekuri

I would open a separate issue for things unrelated to the original issue request.

We have encountered another instance of high CPU usage because of failed merge mutation. @vasicvuk Did you try creating the materialized column `MethodInfo`? It looks like that failed. There was...

@ankitnayan @mindhash I described the changes in our `SigNoz/prometheus` fork here https://github.com/SigNoz/prometheus/pull/13. I tested these changes and am confident about the `/storage` part. Can you confirm the `/rules` changes look...

@nityanandagohain @mindhash ping

Can I get a review/approval on this? I keep fighting the go.mod stash/stash pop, depending on what I am working on.

@ankitnayan can you review this?

It's not the materialized views. Don't run the mutation when the data is large. We have seen this to be the reason from time to time with several customers.

The instant query of Prometheus requires the start and end timestamp to be the same, and it could return multiple series. The returned timestamp in this range is a placeholder...

The timestamps in the result are irrelevant here.

Look at this for example https://play.grafana.org/d/000000012/grafana-play-home?orgId=1