Ability to register multiple metrics with same name

[beam-telemetry]

Ability to register multiple metrics with same name

[bryannaegele]

Hey @ananthakumaran. Whatever is emitting those events is not following standard practices on event naming. The given example has a couple telemetry anti-patterns. The bar and foo in your examples should be a part of the metadata of the event and not part of the event name. Same goes for the pending part.

In the given example, the event should be something like [:<<app_name>>, :queue, :length] with metadata of

%{
  queue: :foo,
  status: :pending
}

Fixing the underlying issue should resolve your predicament.

[ananthakumaran]

I thought I could somehow handle it on the receiver side :). Agree with your point, it should be fixed on the emitter side.

[ananthakumaran]

I ran into the same problem again today with phoenix. I need to capture the duration of all the requests including 500 errors as well, and since phoenix publishes it as two events, there is no way to capture it as a single prometheus metric

[:phoenix, :router_dispatch, :stop]
[:phoenix, :router_dispatch, :exception]

[bryannaegele]

You can combine the two metrics with promql in whatever tooling you are using.