Skip to content

feat: Mark truncated log lines with identifier (backport k261) #18279

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

Merged
merged 1 commit into from
Jun 30, 2025

Conversation

loki-gh-app[bot]
Copy link
Contributor

@loki-gh-app loki-gh-app bot commented Jun 30, 2025

Backport 0ee8e76 from #18262


What this PR does / why we need it:

While truncated JSON log lines are usually easy to identify (because the JSON becomes invalid), it is not always the case with other plain text log lines.

This PR adds the possibility to add an identifier as suffix for truncated log lines, such as [...] so that truncated log lines are easier to spot and identify when querying them.


A truncation identifier has almost been implemented with the initial truncation PR (#4051). This implementation is essentially the same.

While truncated JSON log lines are usually easy to identify (because the JSON becomes invalid), it is not always the case with other plain text log lines.

This PR adds the possibility to add an identifier as suffix for truncated log lines, such as `[...]` so that truncated log lines are easier to spot and identify when querying them.

Signed-off-by: Christian Haudum <christian.haudum@gmail.com>
(cherry picked from commit 0ee8e76)
Copy link
Contributor

github-actions bot commented Jun 30, 2025

💻 Deploy preview deleted.

@chaudum chaudum enabled auto-merge (squash) June 30, 2025 06:38
@chaudum chaudum merged commit dd12872 into k261 Jun 30, 2025
72 checks passed
@chaudum chaudum deleted the backport-18262-to-k261 branch June 30, 2025 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment