Repository navigation
Conversation
Reuse the existing vdev Compose harness and PR review trigger. Compare captured span semantics and multiplicities, require realistic trace coverage, and retain evidence for migration PRs. Generated with GPT-6 (Codex).
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
thomasqueirozb
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
|
/ci-run-e2e-opentelemetry-traces-multiservice |
There was a problem hiding this comment.
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
tessneau
left a comment
There was a problem hiding this comment.
/ci-run-e2e-opentelemetry-traces-multiservice
Summary
Adds a manual OpenTelemetry trace test using the opentelemetry-demo app to Vector's e2e harness.
The existing
opentelemetry-tracese2e test uses telemetrygen, which we could extend to cover more trace cases. However this app produced traces by multiple language SDKs and instrumentation libraries, so we get more varied and realistic input.The main goal is to use this test against PRs against during the trace data model migration (see Trace data model RFC) so that we get the added confidence. This and the heavier application setup (23 services, ~25 min CI run) is why I've kept it manually triggered for now, since I'm not sure you'd want to run this continuously in CI.
Here's the test's architecture:

See the README for details.
References
Related: Trace data model RFC.
Vector configuration
How did you test this PR?
Ran both HTTP and gRPC locally with:
The manually triggered CI run passed on the latest commit
The tests currently takes ~ 25min. Looking into one more change to make it run more quickly in 6cf6484 but this shouldn't change the core
Does this PR include user facing changes?
no-changeloglabel to this PR.Contributor Guidelines
@vectordotdev/vectorto reach out to us regarding this PR.git merge origin masterandgit push.