Skip to content

Document new truncation behaviour in syslog-agent #611

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.

Sign up for GitHub

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
anita-flegg merged 1 commit into from
Sep 28, 2026
Merged

Document new truncation behaviour in syslog-agent #611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions services/log-management.html.md.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,6 +169,10 @@ After a short delay, logs start to flow.

For more information, see [Managing service instances with the CLI](./managing-services.html).

<p class="note">
<strong>Note:</strong> Drained syslog messages identify their source in the RFC5424 <code>PROCID</code> field, which is limited to 128 bytes. Because task names are free text and can be long, a source that exceeds this limit is truncated to fit rather than dropped. The full, untruncated source is always preserved in the <code>source_type</code> structured-data field. To keep <code>PROCID</code> stable and unambiguous in your log management service, keep task names short.
</p>

### <a id='cups-step3'></a> Step 3: Verify that logs are draining

To verify that logs are draining correctly to a third-party log management service:
Expand Down