[azure_metrics] Enable subobjects: false on azure.resource.tags.*

[zmoog]

Proposed commit message

Update azure.resource.tags mapping setting subobjects: true.

On Azure, users can set tag names with dots. When a tag name contains a dot, Elasticsearch expands the dots in the name into an object value, creating a conflict with the expected mapping.

This change allow users to index documents like this:

POST metrics-azure.monitor-pr11345/_doc
{
  "@timestamp": "2024-10-07T12:29:24+02:00",
  "azure": {
    "resource": {
      "id": "795166f8-3743-48dc-9d2e-3807f0375679",
      "tags": {
        "a": 1,
        "tag.with.dots": "value"
      }
    }
  }
}

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.

How to test this PR locally

Related issues

• Closes [azure_metrics]: integration fails ingest metrics when resource tags contain dots in the name #11343

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 36dd77d

Failed CI Steps

• Check integrations azure_metrics

History

• 💚 Build #16853 succeeded c82d324

cc @zmoog

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube