Add `realm` to Oracle Cloud's Resource Detection Processor

[geekdave]

Component(s)

processor/resourcedetection/internal/oraclecloud

Is your feature request related to a problem? Please describe.

The Oracle Cloud Infrastructure (OCI) resource detection processor currently does not expose the "realm" of the running resource as an attribute.

Realms are an Oracle-specific concept that provide a top-level isolation boundary within OCI; each realm encompasses one or more regions and represents a set of data centers with specific compliance or sovereignty characteristics. Not exposing the realm makes it more difficult to distinguish between resources in different real-world or compliance domains, limits multi-tenancy or automation scenarios, and can impede effective observability, especially for customers operating across multiple realms (e.g., public, government, or restricted).

Describe the solution you'd like

Add support for detecting and exporting the Oracle realm as a resource attribute, following OpenTelemetry conventions (e.g., with a vendor-specific prefix such as oraclecloud.realm).

The processor should retrieve the realm information from the Oracle Cloud metadata service and set it as an attribute alongside existing OCI details such as cloud.availability_zone and cloud.region. This enhancement will allow users to filter, group, or analyze telemetry based on realm, improving clarity and compliance auditing for Oracle Cloud infrastructures that span multiple realms.

Describe alternatives you've considered

No response

Additional context

From the OCI docs: https://docs.oracle.com/en-us/iaas/Content/General/Concepts/identifiers.htm#Oracle

Some of the possible values include:

• oc1 for the commercial realm,
• oc2 for the Government Cloud realm
• oc3 for the Federal Government Cloud realm.

Additional realms may be added in the future.

Semantic Conventions?

ℹ️ From chatting with @dashpole , we should use a vendor prefix to add this to the semantic conventions since realm is not a term that's used across vendors. We do not yet have any vendor prefix, so I will propose a separate issue in the semantic conventions repo to add oraclecloud.realm.

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[dashpole]

You should add this to the semantic conventions. You can make a new folder under here for your namespace (oraclecloud): https://github.com/open-telemetry/semantic-conventions/tree/main/model. That helps make the attributes you are adding more discoverable, and includes it in the generated semantic convention constants.