You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old xk6-distributed-tracing extension (until refactoring) had the ability to export the created traces/spans to a tracing backend. This is useful to save additional information (e.g. unique k6-run id) to the spans in order to filter traces in the end. I think generally speaking, not exporting the root span to a trace backend is not really beneficial.
Would be nice to have this feature in the trace module available.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered:
Feature Description
The old xk6-distributed-tracing extension (until refactoring) had the ability to export the created traces/spans to a tracing backend. This is useful to save additional information (e.g. unique k6-run id) to the spans in order to filter traces in the end. I think generally speaking, not exporting the root span to a trace backend is not really beneficial.
Would be nice to have this feature in the trace module available.
Suggested Solution (optional)
No response
Already existing or connected issues / PRs (optional)
No response
The text was updated successfully, but these errors were encountered: