Replace apm-server OTLP endpoint with Otel native processors and Elasticsearch #120
+854
−105
Conversation
This file contains 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
rogercoll
force-pushed
the
otel_native_pipeline
branch
3 times, most recently
from
bc3f7ef to
9a35ecb
Compare
rogercoll
force-pushed
the
otel_native_pipeline
branch
from
9a35ecb to
907bc89
Compare
jasonrhodes
reviewed
Nov 4, 2024
ChrsMark
reviewed
Nov 28, 2024
ChrsMark
approved these changes
Nov 29, 2024
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.
Changes
OpenTelemetry native pipeline using Elastic APM enrichment and aggregation processors. Aligns with 8.16 K8s Onboarding flow configuration: https://github.com/elastic/opentelemetry/blob/8.16/resources/kubernetes/operator/helm/values.yaml
Note: The K8s daemonset could forward the gathered signals to the deployment instance, and just have a collector sending data to Elasticsearch. This PR uses the daemonset to send directly to ES, thus not requiring the deployment collector to collect K8s metrics and logs.
Merge Requirements
For new features contributions, please make sure you have completed the following
essential items:
CHANGELOG.mdupdated to document new feature additionsMaintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.