Yi Jin
Yi Jin
did you get context deadline exceeded (500) from ingestors during the WAL compaction?
We have evidence about dedup logic bug as well, here are the proof: First graph is data points missing when getting the results from thanos receiver with `replicationFactor == 3`,...
seems related to this issue: https://github.com/thanos-io/thanos/issues/981
Yep, you could consider passing a function into ctx so no need to disrupt the query engine itself, reference about how M3 does that: https://github.com/databricks/m3/blob/db_main/src/query/api/v1/handler/prom/read.go#L270-L278 and https://github.com/databricks/m3/blob/db_main/src/query/api/v1/handler/prometheus/handleroptions/headers.go#L121-L123
It is receiver, see more discussions here: https://cloud-native.slack.com/archives/CK5RSSC10/p1719260674748149
+1 see this issue in our setup, left a comment in https://github.com/thanos-io/thanos/pull/7373#issuecomment-2146325916
We found the top metrics cardinality is very useful info to track users' usage, we want a trending view of it instead of instant, so how about making this API...