MetricEventSource value published events don't resolve which scope they are refering to

[noahfalk]

Description

It is supported to have multiple scopes (DI containers effectively) that each have Meters with the same names and same instruments. When the instruments are initially published the scope hash distinguishes those multiple scopes, however later when values are published the scope hash isn't available. This means if two different scopes both have a Meter named Foo and instrument named Bar, the tool listening to the events can't distinguish which one produced the data.

Reproduction Steps

Create two DI containers, then create a Meter and an instrument with identical naming in each. Produce some measurements for both. Enable MetricEventSource and listen to the measurement events.

Expected behavior

The tool should be able to distinguish one set of measurements coming from DI container 1, and a second set of measurements coming from DI container 2.

Actual behavior

There is no distinguishable information that allows correlating the measurements that came from the same DI container together across time.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[noahfalk]

@kkeirstead @tarekgh