Open dmitryax opened 1 year ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Adding release-retro
since this came up in the v0.82.0 release cycle and caused us to release v0.82.1
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 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.
@dmitryax I'm interested in working on this! Would you be able to guide me on what needs to be done?
Add end-to-end tests for the resource detection processor similar to what we have for kubelet and k8s cluster receivers. It'd be hard to get infrastructure for most of the detectors, but at least we can start with
env
andsystem
detectors. Thesystem
detector can be tested on different GH runners + on different containers to imitate failinghost.id
.