Mapped metric name cannot be dynamic about statsd_exporter HOT 5 CLOSED

This limitation is a pretty big blocker preventing statsd_exporter from being a good drop in to get prometheus migration moving along. I imagine I'm not the only person in a shop that has many statsd metrics across many services across many groups of developers which would make writing and maintaining static config from this exporter a near toss up to the complexity of just doing native prometheus instrumentation/exporter for each app.

I can't speak for anyone else's use case, but being able to dynamically name metrics based on capture groups from the statsd names would make the first taste of prometheus from statsd a lot more palatable for our developers.

from statsd_exporter.

Yes, the metric name currently doesn't support this kind of templating, only the other labels. IMO the whole mapper is ripe for a complete overhaul, see also #19.

from statsd_exporter.

any updates on this?

from statsd_exporter.

Is there any estimate on when this will be available?

from statsd_exporter.

This issue is duplicated by #62, but the discussion there has more detail. I'm going to close this one so we can keep the conversations focused.

from statsd_exporter.