Skip to content

[exporterhelper] Create protobuf schema for RequestContext and store in persistent queue #13120

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

Open
jackgopack4 opened this issue May 30, 2025 · 1 comment

Comments

@jackgopack4
Copy link
Contributor

Component(s)

exporter/exporterhelper

Describe the issue you're reporting

If #12934 is landed, this will store spanContext for internal batch tracking span/telemetry as JSON in persistent storage.

But since we have added internal protobuf schema for persistent queue in #13067, there should be ability to define this SpanContext detail in an internal protobuf for increased efficiency in operations.

Alternatively, there could be the ability to save this alongside requests, if the request protobuf schema adds fixed or variable-length byte storage (e.g. marshal SpanContext to internal persistentqueue protobuf, store in pre-allocated byte array in telemetry request).

This should be taken up as follow-up after #12934 is merged; I will be happy to take it up. exporter.PersistRequestContext is in Alpha and this behavior will be behind the featuregate, so even if it were to be a breaking change (which we could mitigate with maintaining fallback logic for a certain number of versions), it would be allowed.

Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

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