[9.0](backport #45242) otel: add otel-specific fields to ingested docs#46498
Closed
mergify[bot] wants to merge 1 commit into9.0from
Closed
[9.0](backport #45242) otel: add otel-specific fields to ingested docs#46498mergify[bot] wants to merge 1 commit into9.0from
mergify[bot] wants to merge 1 commit into9.0from
Conversation
* otel: add otelcol.component.id field to ingested docs * adjust otelcol field name * rename otelcol.component.id in beats event to otel.component.name * add otel.component.type * update metricbeatreceiver unit tests * add integration test coverage * update receiver name in test pipeline * use filestream as receiver name * revert to otelcol.component.id and otelcol.component.kind * fix tests * ignore fields * ignore otel fields in gcppubsub test * move assertion on otel fields to the up * fix linter issues * handle existing otelcol.component.id * prevent otelcol fields from being replaced if they exist * put otelcol fields nested inside agent property * fix E2E tests * use EventuallyWithTf (cherry picked from commit fafbdcb) # Conflicts: # x-pack/filebeat/fbreceiver/receiver_test.go # x-pack/filebeat/input/gcppubsub/otel_test.go # x-pack/filebeat/tests/integration/otel_test.go # x-pack/libbeat/outputs/otelconsumer/otelconsumer.go # x-pack/libbeat/outputs/otelconsumer/otelconsumer_test.go # x-pack/metricbeat/tests/integration/otel_test.go
Contributor
Author
|
Cherry-pick of fafbdcb has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
6 tasks
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Contributor
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Member
|
Closing since we're not backporting otel-related features to 9.0. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
This PR adds the otelcol.component.id and otelcol.component.kind to ingested beats receivers documents. These fields are exclusive to docs ingested by beats receivers and thus not present for standalone beats. In order to avoid conflicts with logs that already have these fields they are nested inside the beats event
agentproperty.See https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/component-universal-telemetry.md#receivers
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
This is an automatic backport of pull request otel: add otel-specific fields to ingested docs #45242 done by Mergify.