Closed mmanciop closed 1 month ago
Pinging code owners:
processor/resourcedetection: @Aneurysm9 @dashpole
See Adding Labels via Comments if you do not have permissions to add labels yourself.
I whipped something up to itch a scratch I have, opened #32859. Also, I'll engage the SemConv SIG to add the missing entries.
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 @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Component(s)
processor/resourcedetection
Is your feature request related to a problem? Please describe.
Collect the following resource attributes from the DigitalOcean droplet metadata endpoint:
cloud.provider
: "digital_ocean" (there is currently no semconv entry for this)cloud.platform
: "droplets" (there is currently no semconv entry for this)cloud.resource_id
: the droplet's id, stringifiedcloud.region
: the DO's regionhost.id
: the droplet's id, stringifiedhost.name
: the droplet's hostnameDescribe the solution you'd like
A new detector in the
resourcedetection
processorDescribe alternatives you've considered
Manual configuration. It's ghastly.
Additional context
No response