Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EPIC] Span V2 Support in Relay #4621

Open
Dav1dde opened this issue Mar 27, 2025 · 0 comments
Open

[EPIC] Span V2 Support in Relay #4621

Dav1dde opened this issue Mar 27, 2025 · 0 comments

Comments

@Dav1dde
Copy link
Member

Dav1dde commented Mar 27, 2025

Background

In preparation for Span Streaming and the EAP Performance rework, there will be a new simplified span schema (let's call it SpanV2 for now).

The new span schema can be found here (TODO link to develop docs once its published).

Envelopes containing these standalone spans can contain spans from multiple segments and multiple different traces, there may be no connection between them. Relay needs to process them independently.

Requirements

Relay will need to:

  • Enforce new standalone span limits
  • Support SpanV2 schema
  • Map from SpanV2 to Span
  • Make the current standalone span processing work for those spans
  • Make sure dynamic sampling works (the trace context is now unique for each span item in the header)

Design

On the protocol level we need a new SpanV2 item. The span item now has the DSC in its header, no longer the envelope.

Envelope Limits:

  • Maximum 1000 spans
  • Maximum 10 MiB envelope

SpanV2 will be (temporarily) mapped to the current span format and produced as such to Kafka.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant