[Azure][Container_registry] Add dimension and metric_type metadata to the container_registry datastream

[tetianakravchenko]

What does this PR do?

• remove duplicated fields

• instead of using wildcard in the field name - use predefined field names

  • for azure.dimensions - there are no dimensions

  Note: only 1 metric - StorageUsed has a dimension, but we do not use it https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-containerregistry-registries-metrics

  • list of metrics - https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-containerregistry-registries-metrics

• used fields for dimensions:

  • cloud.region

  • azure.resource.id - this field includes azure.subscription_id, azure.resource.group, azure.resource.name, format:

     /subscriptions/{azure.subscription_id}/resourceGroups/{azure.resource.group}providers/Microsoft.ContainerRegistry/registries/{azure.resource.name}
    

  • azure.timegrain

    NOTE: there is an issue with timegrain as it does not work as expected, I will create an issue and link it here.

• metrics - use predefined metrics - since in the configuration is defined list of metrics

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-08-16T15:55:32.112+0000

• Duration: 14 min 6 sec

Test stats 🧪

Test	Results
Failed	0
Passed	33
Skipped	0
Total	33

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (3/3)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	73.333% (22/30)	👍
Lines	100.0% (21/21)	💚
Conditionals	100.0% (0/0)	💚

[zmoog]

@tetianakravchenko I see #7162 it is the tracking issue for the timegrain problem.

Do you see this problem as a blocker for this PR?

[agithomas]

Which field will hold the names of the images, tags, other meta data information ? Shouldn't they be dimensions?

[tetianakravchenko]

@agithomas

Which field will hold the names of the images, tags, other meta data information ? Shouldn't they be dimensions?

There is no such information available in this datastream, here is the list of metrics - https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-containerregistry-registries-metrics

as you see those metrics are on the registry level, not for each specific image

all available fields:

[tetianakravchenko]

/test

[agithomas]

LGTM!

[elasticmachine]

Package azure_metrics - 1.0.22 containing this change is available at https://epr.elastic.co/search?package=azure_metrics

[ritalwar]

Typo: "unis" should be "unit".