Julius Volz

> One possible work-around that could be easily(?) implemented in PromLens: As PromLens is already aware of the AST, it is only a small step to make PromLens aware where...

As part of the [`fill()` modifier PR](https://github.com/prometheus/prometheus/pull/17644) and running into issues with [delayed name removal](https://github.com/prometheus/prometheus/pull/17644#discussion_r2597735655) there, I found another type of query that already breaks in current PromQL with the...

Taking this further, I think we have a problem with how the PromQL engine calculates results across steps in general, even with delayed metric name removal disabled (CORRECTION: only with...

Apologies, I made a mistake - my example above also only fails with delayed name removal active, so it's still only a problem with delayed name removal.

Hi @Duncan-dsf, thanks! Comparing the metric names to the best practices / conventions at https://prometheus.io/docs/practices/naming/ and https://prometheus.io/docs/instrumenting/writing_exporters/#naming (specifically for exporters), they look a bit unusual, for example lacking an application...

@Duncan-dsf I see, yeah. For my understanding, are you part of the Volcengine team, or an external user? I'm trying to understand more about this exporter in general. When I...

@bboreham @dgl any input here?

Honestly, it's more of a question of where to put it / whether to put it there again. For the table, we already show some stats right above the table...

@devarsh10 On one hand I like the idea of just showing the exact number next to the automatic resolution values in the dropdown itself. But I just played with it...

Another option I just came up with that is a bit of a middle ground is to show the resolution in the dropdown menu, but in smaller and muted color:...