-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
New component: Alibaba Cloud Resource Detection Processor #35292
Comments
Pinging code owners for processor/resourcedetection: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It's rather an enhancement to an existing component resource detection. However, since we have code owners for each detector, we can follow the same sponsorship approach here. @fatsheep9146 will you have a chance to sponsor this one? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
The purpose and use-cases of the new component
Currently Resource Detection Processor https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/resourcedetectionprocessor/README.md is implemented for all major CSP's - AWS/Azure/GCP - https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor/internal
Would like to request it to be implemented for Alibaba Cloud.
Example configuration for the component
Similar to other CSP config, e.g.
Telemetry data types supported
Same as other implemented CSP's
Is this a vendor-specific component?
Code Owner(s)
No response
Sponsor (optional)
No response
Additional context
It would be great if Otel supported Alibaba Cloud Resource Detection Processor.
The text was updated successfully, but these errors were encountered: