From 25b1e1b6b14e1a3a551b94bb75c426322131d9f4 Mon Sep 17 00:00:00 2001
From: Joris Baum <joris.baum@sap.com>
Date: Mon, 28 Sep 2026 11:32:57 +0200
Subject: [PATCH] Document new truncation behaviour in syslog-agent

The newest syslog-release brings new truncation behaviour in syslog
agent. See
https://github.com/cloudfoundry/loggregator-agent-release/pull/731
---
 services/log-management.html.md.erb | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/services/log-management.html.md.erb b/services/log-management.html.md.erb
index aa9b9214..b153ff34 100644
--- a/services/log-management.html.md.erb
+++ b/services/log-management.html.md.erb
@@ -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: