From 1f8ea7e1f592bcfe811b128f548e4dcfb7f13848 Mon Sep 17 00:00:00 2001 From: Joris Baum Date: Tue, 17 Mar 2026 17:29:08 +0100 Subject: [PATCH 1/3] Use new configuration parameter name for filter --- services/log-management.html.md.erb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/services/log-management.html.md.erb b/services/log-management.html.md.erb index e69ef97e..a4c6d7bd 100644 --- a/services/log-management.html.md.erb +++ b/services/log-management.html.md.erb @@ -98,16 +98,16 @@ You can create a syslog drain service and bind apps to it using Cloud Foundry Co It's important to note that the `drain-data` parameter has precedence over `drain-type`parameter. If the `include-metrics-deprecated` parameter is present in the Syslog URL, the drain forwards logs, application container metrics, and traces. - You can filter which log sources are forwarded to your syslog drain using the `include-source-types` or `exclude-source-types` URL query parameters. The `include-source-types` parameter forwards only logs from the specified source types, while `exclude-source-types` forwards all logs except those from the specified source types. Both parameters accept a comma-separated list of source types, and you can only use one parameter at a time. For a list of valid source types, see [App logging in Cloud Foundry](../deploy-apps/streaming-logs.html). + You can filter which log sources are forwarded to your syslog drain using the `include-log-source-types` or `exclude-log-source-types` URL query parameters. The `include-log-source-types` parameter forwards only logs from the specified source types, while `exclude-log-source-types` forwards all logs except those from the specified source types. Both parameters accept a comma-separated list of source types, and you can only use one parameter at a time. For a list of valid source types, see [App logging in Cloud Foundry](../deploy-apps/streaming-logs.html). Example: Forward only application and router logs: 
-    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?include-source-types=app,rtr
+    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?include-log-source-types=app,rtr
Example: Forward all logs except staging logs: 
-    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?exclude-source-types=stg
+    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?exclude-log-source-types=stg
If you are using the mTLS feature delivered in [CAPI release 1.143.0](https://github.com/cloudfoundry/capi-release/releases/tag/1.143.0), you can use the `-p` flag to define the client certificate and key as credentials, filling in values as follows.
From adb0f6e001ba30015d9d4052fbde6ddca8ac059a Mon Sep 17 00:00:00 2001 From: Joris Baum Date: Tue, 17 Mar 2026 17:29:34 +0100 Subject: [PATCH 2/3] Document behavior on missing source type. ..even though this is unlikely to be encountered (most envelopes have a source type). --- services/log-management.html.md.erb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/services/log-management.html.md.erb b/services/log-management.html.md.erb index a4c6d7bd..d6059a60 100644 --- a/services/log-management.html.md.erb +++ b/services/log-management.html.md.erb @@ -100,6 +100,8 @@ You can create a syslog drain service and bind apps to it using Cloud Foundry Co You can filter which log sources are forwarded to your syslog drain using the `include-log-source-types` or `exclude-log-source-types` URL query parameters. The `include-log-source-types` parameter forwards only logs from the specified source types, while `exclude-log-source-types` forwards all logs except those from the specified source types. Both parameters accept a comma-separated list of source types, and you can only use one parameter at a time. For a list of valid source types, see [App logging in Cloud Foundry](../deploy-apps/streaming-logs.html). + When using `include-log-source-types`, logs with a missing or unrecognized source type are dropped. When using `exclude-log-source-types`, logs with a missing or unrecognized source type are forwarded. + Example: Forward only application and router logs: 
     $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?include-log-source-types=app,rtr

From f537532c043e84d77a21036cde294d16099d352f Mon Sep 17 00:00:00 2001
From: Jovan Kostovski 
Date: Wed, 5 Aug 2026 15:28:35 +0200
Subject: [PATCH 3/3] Update the docs after parameter renaming

Co-authored-by: Joris Baum 
---
 services/log-management.html.md.erb | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/services/log-management.html.md.erb b/services/log-management.html.md.erb
index d6059a60..aa9b9214 100644
--- a/services/log-management.html.md.erb
+++ b/services/log-management.html.md.erb
@@ -98,18 +98,18 @@ You can create a syslog drain service and bind apps to it using Cloud Foundry Co
 
     It's important to note that the `drain-data` parameter has precedence over `drain-type`parameter. If the `include-metrics-deprecated` parameter is present in the Syslog URL, the drain forwards logs, application container metrics, and traces.
 
-    You can filter which log sources are forwarded to your syslog drain using the `include-log-source-types` or `exclude-log-source-types` URL query parameters. The `include-log-source-types` parameter forwards only logs from the specified source types, while `exclude-log-source-types` forwards all logs except those from the specified source types. Both parameters accept a comma-separated list of source types, and you can only use one parameter at a time. For a list of valid source types, see [App logging in Cloud Foundry](../deploy-apps/streaming-logs.html).
+    If you are not interested in some log types or they cause overloading in your backend, you can specify which log types are forwarded with your syslog drain using the `include-log-types` or `exclude-log-types` Syslog URL query parameters. The `include-log-types` parameter forwards only logs from the specified log types, while `exclude-log-types` forwards all logs except those from the specified log types. Both parameters accept a comma-separated list of log types, and you can only use one parameter at a time. For a list of valid log types, see [App logging in Cloud Foundry](../deploy-apps/streaming-logs.html).
 
-    When using `include-log-source-types`, logs with a missing or unrecognized source type are dropped. When using `exclude-log-source-types`, logs with a missing or unrecognized source type are forwarded.
+    When using `include-log-types`, logs with a missing or unrecognized log type are dropped. When using `exclude-log-types`, logs with a missing or unrecognized log type are forwarded.
 
     Example: Forward only application and router logs:
     
-    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?include-log-source-types=app,rtr
+    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?include-log-types=app,rtr
     

 
     Example: Forward all logs except staging logs:
     
-    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?exclude-log-source-types=stg
+    $ cf create-user-provided-service my_app_drain -l syslog://logs.example.com:1234?exclude-log-types=stg
     

 
     If you are using the mTLS feature delivered in [CAPI release 1.143.0](https://github.com/cloudfoundry/capi-release/releases/tag/1.143.0), you can use the `-p` flag to define the client certificate and key as credentials, filling in values as follows.