add support for replaying to OTLP endpoints #45
Conversation
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
Contributor
Author
|
At the moment I'm stuck debugging the handler logic around creating batches, which for the OTLP case produce a segfault. I suspect this is due to the different data format on which the same transform operations don't work as expected. (note to self, why not implementing |
endorama
force-pushed
the
support-otlp-http
branch
from
9c9a470 to
ff50195
Compare
Contributor
Author
|
I extracted the relevant refactoring to accomodate this functionality in #46. This PR will be based on top of that branch, with additional commits to implement OTLP support. |
endorama
force-pushed
the
support-otlp-http
branch
from
ff50195 to
859bc2a
Compare
JSONL is the suggested format in current otel File Exporter (experimental). https://opentelemetry.io/docs/specs/otel/protocol/file-exporter/#json-lines-file
endorama
force-pushed
the
support-otlp-http
branch
from
859bc2a to
6b0a993
Compare
Contributor
Author
|
Rebase completed, this branch now only include changes relevant to the OTLP support. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR enhance
apmsoakwith the capability to replay otel data to OTLP backend endpoints.Creating sample files is possible using the (experimental) otel File Exporter. At the moment this PR is using sample data from here.
There have been some challenges in adapting
apmsoakfor the OTLP use case:agent_nameconfig in scenario file: agents starting withapmare considered Elastic APM agents whereas agents starting withotlpare considered differently. By matching agent name forotlp-logs,otlp-metricsandotlp-tracesis also possible to select the appropriate data to replay.jsonlines(.jsonl) file format; we are usingndjson. The 2 formats should be compatible but I haven't fully investigated the details. OTLP sample files are sources from.jsonlfiles.otlp/grpcis not supported.Closes #18