Skip to content

feat(spans): Skip enrichment when message contains skip_enrichment=True flag#112024

Merged
lvthanh03 merged 1 commit intomasterfrom
tony/process-segments-skip-enrichment
Apr 8, 2026
Merged

feat(spans): Skip enrichment when message contains skip_enrichment=True flag#112024
lvthanh03 merged 1 commit intomasterfrom
tony/process-segments-skip-enrichment

Conversation

@lvthanh03
Copy link
Copy Markdown
Member

Going off of product requirements from #111820 (comment), we want to have a way to signal the process-segments consumer to skip enrichment once a segment hits the size limit.

When this happens, the process-spans consumer would produce the segment in chunks to the buffered-segments topic, where each message contains one chunk along with the flag skip_enrichment=True.

@lvthanh03 lvthanh03 requested review from a team as code owners April 1, 2026 18:21
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 1, 2026
@lvthanh03 lvthanh03 merged commit 1ea2a6c into master Apr 8, 2026
66 checks passed
@lvthanh03 lvthanh03 deleted the tony/process-segments-skip-enrichment branch April 8, 2026 16:35
george-sentry pushed a commit that referenced this pull request Apr 9, 2026
…ue flag (#112024)

Going off of product requirements from
#111820 (comment),
we want to have a way to signal the process-segments consumer to skip
enrichment once a segment hits the size limit.

When this happens, the process-spans consumer would produce the segment
in chunks to the buffered-segments topic, where each message contains
one chunk along with the flag `skip_enrichment=True`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants