Add Resource Detection processor to OTel mode#4811
Add Resource Detection processor to OTel mode#4811michalpristas merged 17 commits intoelastic:mainfrom
Conversation
For some reason the `go.sum` file contains an update to the dependency `github.com/pascaldekloe/goe`, and go-licence-detector cannot detect the license, which is CC0-1.0. I have added an override for the package and also added CC0-1.0 to allowed licenses.
|
This pull request does not have a backport label. Could you fix it @andrzej-stencel? 🙏
NOTE: |
|
Proposed and merged this change to resolve the dependency conflict: Once this is released in a new version of the |
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
seems like you have to resolve som go.mod conflicts but other than that it looks ok |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
|
* Add Resource Detection processor to OTel mode * go mod tidy * make notice For some reason the `go.sum` file contains an update to the dependency `github.com/pascaldekloe/goe`, and go-licence-detector cannot detect the license, which is CC0-1.0. I have added an override for the package and also added CC0-1.0 to allowed licenses. * mage otel:readme * Add changelog entry * update `elastic-agent-autodiscover` to `v0.7.0` * make notice * go mod tidy * mage update * make notice --------- Co-authored-by: Michal Pristas <michal.pristas@gmail.com> (cherry picked from commit a5a4a3b) # Conflicts: # NOTICE.txt # go.mod # go.sum # internal/pkg/otel/README.md # internal/pkg/otel/components.go # internal/pkg/otel/testdata/all-components.yml
This reverts commit d06dcf6.




What does this PR do?
This PR makes the Resource Detection processor available to users running Elastic Agent in
otelmode.Why is it important?
This allows users to enrich the collected telemetry with metadata of the infrastructure, e.g.
host.name,os.type,cloud.provider,cloud.region,k8s.cluster.nameand many more.Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
No impact expected.
How to test this PR locally
build/distributions