Nick Pillitteri

Can you explain why you'd want Mimir/Tempo/etc to listen on a UNIX socket?

> Oh right: I want to run a reverse proxy (nginx) in front of its API, and I'd prefer not to run the risk of exposing it over the network....

Redis support is experimental and unsupported. IMO it shouldn't have ever been added to dskit or Mimir. We don't run it and have no intention of running it. I propose...

> > Redis support is experimental and unsupported. IMO it shouldn't have ever been added to dskit or Mimir. We don't run it and have no intention of running it....

Note that if you are running Mimir, the helm chart and jsonnet configure Memcached for you. We (Grafana) don't run Redis internally for Mimir and so can't support it as-is....

How is this different than the current behavior?

Could you explain why you think this relates to dskit?

@kavirajk The flagext from Cortex was already ported to dskit. What specifically is the one in dskit missing compared to loki's copy? I'm closing this since Loki has already been...

I'm able to reproduce this locally. It appears to be caused by [our error translation code](https://github.com/grafana/mimir/blob/bf7557130e67a36ff2d6909b7de84e08c4fb334c/pkg/querier/error_translate_queryable.go) not covering the entire querier hierarchy (queryable -> querier -> series set -> series...

FYI, since this was opened we've added bytes processed to the `Server-Timing` header per https://github.com/grafana/mimir/pull/9645. If this gets worked on, please use that header as well _or_ update both places...