[Azure] Fix the metrics field name in the container instance datastream

[zmoog]

What does this PR do?

Fix the rename processor to use the correct field name. Add aliases to allow existing users to access all data with the old field names azure.metrics.* for backwards compatibility.

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

• Fix rename processor
• Add aliases for the azure.metrics.* field names

How to test this PR locally

Aliases for backwards compatibility

Existing users can use field names azure.metrics.*in dashboards and queries to access old and new documents:

In the metrics-azure.container_instance-default there are:

• 12 documents created with integration v1.0.23, having azure.metrics fields only.
• 22 documents created with integration v1.0.24, having azure.container_instance fields only.

#
# request
#

POST metrics-azure.container_instance-default/_search
{
  "query": {
    "exists":{
      "field":"azure.metrics"
    }
  }
}

#
# response
#

{
  "hits": {
    "total": {
      "value": 34,
      "relation": "eq"
    },


#
# request
#

POST metrics-azure.container_instance-default/_search
{
  "query": {
    "exists":{
      "field":"azure.container_instance"
    }
  }
}

#
# response
#

{
  "hits": {
    "total": {
      "value": 22,
      "relation": "eq"
    },

If we query azure.container_instance we get the 22 new docs only. However, if we query using azure.metrics we get all 34 (12 + 22) documents.

Related issues

• Closes [Azure] [container_instance] Not correct metrics field #7158

Screenshots

The dashboard can show data now that the pipeline creates the documents with the expected field names.

[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-22T14:32:08.175+0000

• Duration: 14 min 44 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)	👎 -15.556
Lines	100.0% (21/21)	💚 9.333
Conditionals	100.0% (0/0)	💚

[rajvi-patel-22]

Looks good to me!

[tetianakravchenko]

changelog and manifest version update are missing, could you please add it?

maybe it makes sense to update the relevant dashboards with the correct metric naming? for example: If I install fixed version of integration, it might be confusing to find that used azure.metrics... instead of expected azure.container_instance, @zmoog wdyt?

[zmoog]

changelog and manifest version update are missing, could you please add it?

🤦

I added the missing changelog entry, thanks!

maybe it makes sense to update the relevant dashboards with the correct metric naming? for example: If I install fixed version of integration, it might be confusing to find that used azure.metrics... instead of expected azure.container_instance, @zmoog wdyt?

The dashboards was already using azure.container_instance.* field names. Without this change, the dashboard does not display anything. I am surprised we didn't receive and SDH or other bug report about problem.

[endorama]

Add aliases to allow existing users to access all data with the old field names azure.metrics.* for backwards compatibility.

🤩

[zmoog]

Add aliases to allow existing users to access all data with the old field names azure.metrics.* for backwards compatibility.

🤩

If you break it, you fix it ™

[elasticmachine]

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