Add semantic conventions for Azure subscription ID and resource group

[kathiehuang]

Fixes #3697
Fixes #3708

Changes

Adds two Azure resource conventions that are already used in practice by the OpenTelemetry collector-contrib azurevm resource detector but were not formally defined:

• azure.resourcegroup.name (new attribute): The name of the Azure resource group the resource belongs to.

• cloud.account.id (updated note + example): Documents that for Azure, this attribute maps to the subscription ID, and adds a UUID-format example.

Naming note: azure.resourcegroup.name uses a single-token resourcegroup rather than the semconv underscore form azure.resource_group.name. This intentionally matches the name already emitted by the azurevm detector in collector-contrib. The semconv form would be azure.resource_group.name.

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)
  • azure.resourcegroup.name is already emitted by the azurevm detector in resourcedetectionprocessor and referenced multiple times in collector-contrib
  • cloud.account.id for Azure subscription ID is already used in practice by the same detector

[github-actions]

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

• azure
• cloud

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

[kathiehuang]

@lmolkova @MikeGoldsmith @thompson-tomo @trask

Hi all - I saw you had contributed to the Azure semantic conventions in the past. This PR formalizes two Azure attributes that are already emitted in practice by the azurevm resource detector in opentelemetry-collector-contrib but have no official spec definition:

• azure.resourcegroup.name - documented in the Azure resourcedetectionprocessor and appears in the OTel specification Resource and Entities OTEP
• cloud.account.id - used by the existing Azure VM resource detector for subscription IDs

I was wondering if it would be possible to reopen this PR and get a review. Thank you!

[MikeGoldsmith]

Hi @kathiehuang — sorry for the slow reply.

I think what you've proposed looks good from a technical view.

One thing worth noting is the attribute key azure.resourcegroup.name uses a single-token "resourcegroup", whereas the semconv convention for multi-word segments is underscore (e.g. cloud.availability_zone, cloud.resource_id, aws.lambda.invoked_arn). The "by-convention" form would be azure.resource_group.name. Picking the current form matches the existing collector-contrib usage - picking the conventional form would force a rename for consumers. I think it's worth calling out the choice explicitly in the PR description so reviewers can see you've considered it.

The actual blocker isn't technical — the auto-close was triggered by the lack of an active SIG for the azure and cloud areas, per the bot message. I have reopen access, so I can reopen this PR and help move it forward. Apologies again for the delayed response.

[MikeGoldsmith]

Looks good to me. I've noted a few things but the only thing to do is combine the two changelog entries.

[MikeGoldsmith]

I think these notes are good to help indicate what to expect per cloud provider.

[github-actions]

This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:

• azure
• cloud

Such changes may be rejected or put on hold until a new SIG/project is established.

Please refer to the Semantic Convention Areas
document to see the current active SIGs and also to learn how to kick start a new one.

[MikeGoldsmith]

Thanks @trask 👍🏻