Oracle Cloud Resource Detection Processor

[geekdave]

Description

Implements a resource detection processor for Oracle Cloud Infrastructure (OCI) to enrich telemetry with environment metadata.

Uses semantic conventions for OCI: open-telemetry/semantic-conventions#1720

Link to tracking issue

Fixes #35091

Testing

• Added unit tests following existing conventions
• Built custom otel collector using ocb, ran on Oracle Kubernetes Engine (OKE) cluster, and verified that resulting metrics are enriched with these labels:

Documentation

• Updated processor documentation (processor/resourcedetectionprocessor/README.md) to describe Oracle Cloud detection usage and configuration.
• Added Go docstrings and inline comments for maintainability.

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Please review our Contributing Guidelines.
• Don't forget to sign the Contributor License Agreement (CLA) if you haven't already.

A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better!

[atoulme]

Will you be owning this code moving forward?

[geekdave]

@atoulme Yes! I, along with two of my colleagues at Oracle, @tonychoe and @raphaelfan can be the codeowners.

We discussed ownership and project sponsorship with @dashpole (who volunteered to be the project sponsor) in this linked issue:
#35091

[dashpole]

Feel free to ping me on slack once tests are passing

[github-actions]

Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib.

Important reminders:

• Please review our Contributing Guidelines.
• Don't forget to sign the Contributor License Agreement (CLA) if you haven't already.

A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better!

[atoulme]

Moving to draft while you work out the issues, please mark ready for review when CI passes.

[geekdave]

@atoulme Tests are now passing! I've been working with @dashpole who has been helping to manually trigger test runs. The most recent run passed. However, when I clicked on Ready for Review it seems to have cleared the recent test results. It may require a re-trigger?

[geekdave]

Also wanted to mention that I tried to add myself and my Oracle teammates as codeowners in our metadata.yaml file, but CI failed because we are not members of the OTel GitHub Org. @dashpole mentioned this is a classic "chicken and egg" problem. For now I removed us from the list. But I wanted to reiterate that we are committed to maintaining and supporting this component. I'm looking forward to participating in meaningful ways to work towards earning org membership (and codeowner status)!

[atoulme]

@geekdave you can add yourself to the allowlist under cmd/githubgen/allowlist.txt one username per line if you would like to be codeowners ahead of joining as members. Or we can add you post facto.

I have triggered the build.

[atoulme]

@dashpole please review

[geekdave]

@atoulme Thanks for the tip! If it's alright I will hold my breath and back away slowly from this PR's green CI status, and update the allowlist as a follow-up PR after-the-fact. 😉