Conversation
Two things changed under this page. Extensions export spans of their own since extension-kit v1.12.1, so a trace now covers the platform, the agent and the extension it called rather than stopping at the agent. And the platform's per-run span download is being retired, so the page can no longer point at it. Replaces the download section with how to find a run in your own backend: every span carries the run's experiment.execution.id, so one query pulls up everything that happened during it. The time-window caveat is called out because a default of "last 1 hour" returns nothing for an older run, which looks exactly like the traces being missing. Adds an extension configuration section: the OTEL_* variables, the otel Helm values including the global block that configures every extension at once, and a warning that the gRPC default pairs with port 4317 — pointing it at an OTLP/HTTP collector on 4318 without changing the protocol exports nothing. Drops the "experimental" note on export. With the platform-side collection going away this is the only path, so labelling it experimental is misleading.
docs_lint's table-width rule requires every row in a table to be the same character width; the new query and configuration tables were ragged.
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
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.
Two things changed under this page:
extension-kitv1.12.1 (feat: add OpenTelemetry HTTP tracing support extension-kit#114, Update Windows compatibility matrix with missing attack categories #179, Feat/risk #180). A trace now covers the platform, the agent and the extension it called, rather than stopping at the agent — which is what makes a timing-out action debuggable.What changed
Replaced the "Download through the Experiment Run View" section with "Finding the Traces for an Experiment Run". Every span of a run carries an
experiment.execution.idattribute, so a single query pulls up everything that happened during it:{ span.experiment.execution.id = "138004" }experiment.execution.id=138004@experiment.execution.id:138004The time-window caveat is called out deliberately: tracing backends search a window rather than all history, so a default of "last 1 hour" returns nothing for an older run — indistinguishable from the traces being missing.
Added an "Extension Configuration" section: the
OTEL_*variables, theotelHelm values including theglobal.otelblock that configures every extension in a release at once, and a warning that the gRPC default pairs with port 4317 — pointing it at an OTLP/HTTP collector on 4318 without changing the protocol exports nothing, silently.Dropped the "experimental capability" note on export. With platform-side collection going away this becomes the only path, so the label is misleading.
Removed
traces-download.png, now orphaned.Merge timing
Best merged alongside or just after steadybit/platform#2036, since it describes the run view as showing the identifier and queries.
Vendor coverage
Deliberately limited to Tempo, Jaeger and Datadog. Those three I can state confidently; for others the attribute may not be queryable as written — AWS X-Ray only indexes annotations, and Elastic transforms attribute keys — and a wrong query in the docs is worse than none, since it sends people hunting for traces that are actually there.