I have a cluster which emits a very high amount of metrics from the Historical service. These metrics are for per-segment reads (query/segment/time, query/wait/time). Is there a working way to disable these specific metrics without code change?
At this time the best way to disable those specific metrics is through an extension that defines a custom QueryMetrics implementation. This is a bit technical, though, and so the goal is to be able to do it via configuration.
Fwiw, if you are using the Imply distro’s Clarity emitter (which supports HTTP or Kafka) you can disable or sample any metrics via configuration. That is via configuration for that specific emitter extension, though, rather than a general thing that works for all emitters.