Metadata is returned as 'None' when querying metrics with filter parameter

[kshilovskiy]

• Package Name: azure-monitor-query
• Package Version: 1.0.0
• Operating System: Mac OS 11.4
• Python Version: 3.9.7

Describe the bug
I am trying to get the eventhub namespace metrics split by the eventhub name. Therefore I am using * as the filter value: entityname eq '*'.
The returned data is indeed split by the entity name. However there is no metadata provided. So I am not able to understand
what entities the values belong too.

To Reproduce
I am using this code:

metrics_uri = os.environ['METRICS_RESOURCE_URI']

response = client.query_resource(
    metrics_uri,
    metric_names=["IncomingMessages"],
    timespan=timedelta(days=1),
    granularity=timedelta(hours=24),
    filter="entityname eq '*'",
    aggregation='Total'
)

for metric in response.metrics:
    print(metric.name + ' -- ' + metric.display_description)
    for time_series_element in metric.timeseries:
        print(f"Metadata {time_series_element.metadata_values}")
        for metric_value in time_series_element.data:
            print(f"{metric_value.timestamp} -- {metric_value.total}")

METRICS_RESOURCE_URI is the the eventhub namespace.

Expected behavior
Metadata is returned and contains the name of the event hub.

Screenshots
Here is the output from the above code

Additional context
The metadata is returned correctly with Azure CLI

[mccoyp]

Hi @kshilovskiy, thank you for opening an issue! I'll tag the appropriate folks so we can take a look at this as soon as possible.

[rakshith91]

Hi @kshilovskiy, Thanks for reporting the issue - it will be fixed in this PR #21513 and will be released in the upcoming release next week.

[ghost]

Hi @kshilovskiy. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[rakshith91]

@kshilovskiy The issue is addressed and will be pushed to release early next week. Thanks a lot for reporting this

[ghost]

Hi @kshilovskiy, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.