Area(s)

area:cloud

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

I'm an engineer at Oracle working on adding support for Oracle Cloud Infrastructure to the OTel Collector Contrib, in the form of a new Resource Detection Processor. See: open-telemetry/opentelemetry-collector-contrib#35091

As part of this work, we'd like to define new semantic conventions that we can utilize in that project, to avoid hardcoding names for cloud.provider and cloud.platform.

Describe the solution you'd like

We generally use the acronym OCI to refer to Oracle Cloud Infrastructure however @dashpole advised us that we may want to avoid using oci in the conventions, since that is currently used for the open container initiative.

Instead, I propose that we use oracle_cloud in the id and value properties, and the full Oracle Cloud Infrastructure (OCI) name in the brief field, like so:

cloud.provider:

            - id: 'oracle_cloud'
              value: 'oracle_cloud'
              brief: 'Oracle Cloud Infrastructure (OCI)'
              stability: experimental

We'd also like to define two additions to the cloud.platform area, as these will be used in our Resource Detection Processor mentioned above.

cloud.platform:

            - id: oracle_cloud_compute
              value: 'oracle_cloud_compute'
              brief: Compute on Oracle Cloud Infrastructure (OCI)
              stability: experimental
            - id: oracle_cloud_oke
              value: 'oracle_cloud_oke'
              brief: Kubernetes Engine (OKE) on Oracle Cloud Infrastructure (OCI)
              stability: experimental

Describe alternatives you've considered

No response

Additional context

No response