-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[processor/resourcedetection] support openstack nova into resourcedetection processor #41973
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ection processor Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
processor/resourcedetectionprocessor/internal/openstack/nova/metadata.yaml
Show resolved
Hide resolved
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
|
@paulojmdias would you like to become the codeowner of this code path? We will need your expertise to maintain this code. |
|
@atoulme sure yes 🙏 I appreciate the invite and I really want to continue helping the community 🙌 |
I am pinging you on the CNCF slack with instructions. |
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
/label never-stale -stale |
…-contrib into feat/39117 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…-contrib into feat/39117 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
|
I added myself as a code owner, together with the parent codeowners of |
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
/label -stale never-stale |
…-contrib into feat/39117 Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
…ection processor (open-telemetry#41973) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR introduces a new resource detection processor for OpenStack Nova, similar to the existing AWS EC2 and GCP GCE detectors. It uses the Nova instance metadata service to populate standard `cloud.*` and `host.*` attributes, and optionally captures selected meta labels as resource attributes based on user-defined regex filters. Despite the current semantic convention discussion in open-telemetry/semantic-conventions#2622, I made this PR ready for review for the code and discussed improvements. So when this PR was marked ready for review, the following values were set hardcoded temporarily. ```go d.rb.SetCloudProvider("openstack") d.rb.SetCloudPlatform("openstack_nova") ``` <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39117 <!--Describe what testing was performed and which tests were added.--> #### Testing I tested against OpenStack instances, and the output was the expected. ```sh Resource attributes: -> host.type: Str(REDACTED) -> cloud.provider: Str(openstack) -> cloud.platform: Str(openstack_nova) -> cloud.account.id: Str(REDACTED) -> cloud.availability_zone: Str(REDACTED) -> host.id: Str(680a44a7-a2f1-40bc-9b19-6f6ad9592290) -> host.name: Str(instance01) -> openstack.nova.meta.key1: Str(value1) -> openstack.nova.meta.key2: Str(value2) ``` I also added tests to cover all the cases. If I'm missing something, please let me know. <!--Describe the documentation added.--> #### Documentation Added documentation for how to enable the detection for `nova` and also the docs generated with `mdatagen`. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <paulodias.gm@gmail.com> Co-authored-by: Antoine Toulme <atoulme@splunk.com>
…ection processor (open-telemetry#41973) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR introduces a new resource detection processor for OpenStack Nova, similar to the existing AWS EC2 and GCP GCE detectors. It uses the Nova instance metadata service to populate standard `cloud.*` and `host.*` attributes, and optionally captures selected meta labels as resource attributes based on user-defined regex filters. Despite the current semantic convention discussion in open-telemetry/semantic-conventions#2622, I made this PR ready for review for the code and discussed improvements. So when this PR was marked ready for review, the following values were set hardcoded temporarily. ```go d.rb.SetCloudProvider("openstack") d.rb.SetCloudPlatform("openstack_nova") ``` <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39117 <!--Describe what testing was performed and which tests were added.--> #### Testing I tested against OpenStack instances, and the output was the expected. ```sh Resource attributes: -> host.type: Str(REDACTED) -> cloud.provider: Str(openstack) -> cloud.platform: Str(openstack_nova) -> cloud.account.id: Str(REDACTED) -> cloud.availability_zone: Str(REDACTED) -> host.id: Str(680a44a7-a2f1-40bc-9b19-6f6ad9592290) -> host.name: Str(instance01) -> openstack.nova.meta.key1: Str(value1) -> openstack.nova.meta.key2: Str(value2) ``` I also added tests to cover all the cases. If I'm missing something, please let me know. <!--Describe the documentation added.--> #### Documentation Added documentation for how to enable the detection for `nova` and also the docs generated with `mdatagen`. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <paulodias.gm@gmail.com> Co-authored-by: Antoine Toulme <atoulme@splunk.com>
Description
This PR introduces a new resource detection processor for OpenStack Nova, similar to the existing AWS EC2 and GCP GCE detectors.
It uses the Nova instance metadata service to populate standard
cloud.*andhost.*attributes, and optionally captures selected meta labels as resource attributes based on user-defined regex filters.Despite the current semantic convention discussion in open-telemetry/semantic-conventions#2622, I made this PR ready for review for the code and discussed improvements. So when this PR was marked ready for review, the following values were set hardcoded temporarily.
Link to tracking issue
Fixes #39117
Testing
I tested against OpenStack instances, and the output was the expected.
Resource attributes: -> host.type: Str(REDACTED) -> cloud.provider: Str(openstack) -> cloud.platform: Str(openstack_nova) -> cloud.account.id: Str(REDACTED) -> cloud.availability_zone: Str(REDACTED) -> host.id: Str(680a44a7-a2f1-40bc-9b19-6f6ad9592290) -> host.name: Str(instance01) -> openstack.nova.meta.key1: Str(value1) -> openstack.nova.meta.key2: Str(value2)I also added tests to cover all the cases. If I'm missing something, please let me know.
Documentation
Added documentation for how to enable the detection for
novaand also the docs generated withmdatagen.