feat: SLS-389: add batch ID to log messages - #562
Open
jhcipar wants to merge 2 commits into
Open
Conversation
jhcipar
marked this pull request as ready for review
August 4, 2026 17:58
jhcipar
changed the title
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.
Summary
When batchId is set on a particular job, this threads batch id through and sets it via a context var for workers so that jobs associated with a particular batch include the batch id in log statements.
Motivation
The existing Tinybird log pipeline preserves message text but drops additional structured fields. Adding the batch token to the message enables filtering without a Tinybird schema migration.
Verification
Related