From 8b46835f264a10a15436b9f3b8f1b962db28eb1f Mon Sep 17 00:00:00 2001 From: Luana Dos Santos Date: Fri, 6 Mar 2026 17:46:38 -0300 Subject: [PATCH 1/8] W-19120572-console-logging --- .../modules/ROOT/pages/ps-config-advanced.adoc | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc index b560817a..8c443f3d 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc @@ -9,7 +9,7 @@ This value is the amount of time the CloudHub 2.0 ingress controller waits to re + [IMPORTANT] ==== -This timeout setting is separate from the read-request timeout, which controls how long the CloudHub 2.0 ingress controller waits to receive the full request from the client. The read-request timeout is hardcoded to 300 seconds, and you can't configure it. If your client takes longer than 300 seconds to send the complete request (for example, when uploading large files), CloudHub 2.0 drops the connection even if you have configured a longer read-response timeout. +This timeout setting is separate from the read-request timeout, which controls how long the CloudHub 2.0 ingress controller waits to receive the full request from the client. The read-request timeout is hardcoded to 300 seconds and isn't configurable. If your client takes longer than 300 seconds to send the complete request, for example, when uploading large files, CloudHub 2.0 drops the connection even if you configure a longer read-response timeout. For data transfers that exceed 300 seconds, consider breaking the request into smaller chunks or implementing asynchronous processing patterns. ==== @@ -19,7 +19,7 @@ For data transfers that exceed 300 seconds, consider breaking the request into s == Configure HTTP Requests and Read-Response Timeout -When you modify HTTP requests, applications may not be reachable for up to 5 seconds. +When you modify HTTP requests, applications aren't reachable for up to 5 seconds. // SELECT PRIVATE SPACE SHARED include::partial$select-private-space.adoc[tag=selectPrivateSpace] @@ -44,7 +44,7 @@ Silently drops HTTP requests. -- . Specify the read response timeout value. + -The default read-response timeout is 300 seconds. You can configure this value up to 3600 seconds (1 hour). +The default read-response timeout is 300 seconds. Configure this value up to 3600 seconds (1 hour). + . Click *Save Changes* or *Discard Changes*. @@ -60,7 +60,7 @@ Read Request Timeout (hardcoded at 300 seconds):: The time the CloudHub 2.0 ingress controller waits to receive the complete request from the client. If the client takes longer than 300 seconds to send the entire request payload (for example, uploading a large CSV file), CloudHub 2.0 drops the connection. This timeout is not user-configurable and applies to both shared and private spaces. Read Response Timeout (user-configurable):: -The time the CloudHub 2.0 ingress controller waits to receive a response from your Mule application after the request has been forwarded. You can configure this timeout in the *Advanced* tab of your private space settings. This setting controls how long your Mule application has to process the request and begin sending a response. +The time the CloudHub 2.0 ingress controller waits to receive a response from your Mule application after the request has been forwarded. Configure this timeout in the *Advanced* tab of your private space settings. This setting controls how long your Mule application takes to process the request and begin sending a response. Connection Idle Timeout (hardcoded at 15 seconds):: The time the CloudHub 2.0 ingress controller waits before closing an idle connection when no data is being transferred. @@ -77,7 +77,7 @@ For long-running operations that exceed these timeout limits, consider implement CloudHub 2.0 enables you to specify the default severity level of messages that are written to the log file for all apps deployed to the private space. [IMPORTANT] -More verbose log levels might affect performance. +More verbose log levels affect performance. // SELECT PRIVATE SPACE SHARED include::partial$select-private-space.adoc[tag=selectPrivateSpace] @@ -92,7 +92,7 @@ include::partial$select-private-space.adoc[tag=clickAdvanced] CloudHub 2.0 enables you to specify the default severity level of messages that are written to the log file for specific IP addresses, for example, for troubleshooting. [IMPORTANT] -More verbose log levels might affect performance. +More verbose log levels affect performance. // SELECT PRIVATE SPACE SHARED include::partial$select-private-space.adoc[tag=selectPrivateSpace] @@ -149,7 +149,7 @@ include::partial$select-private-space.adoc[tag=clickAdvanced] [[configure-aws-role]] == Configure AWS Service Role -If you have identity and access management (IAM) roles configured in AWS, you can associate the role with your private space. The private space receives the permissions from the IAM role in AWS and can access AWS resources. To configure this feature in AWS: +If you have identity and access management (IAM) roles configured in AWS, associate the role with your private space. The private space receives the permissions from the IAM role in AWS and accesses AWS resources. To configure this feature in AWS: * Use the unique AWS IAM role name that Anypoint Platform generates. * Use the organization ID for the organization in which the private space was configured. @@ -164,10 +164,10 @@ include::partial$select-private-space.adoc[tag=clickAdvanced] . Click *Enable AWS Service Role*. . Click *Save Changes* or *Discard changes*. + -A unique service role name is generated, and you can use this role configure to configure identity and access management for AWS. Role generation might take a few minutes. If the role name does not appear, refresh the page. +A unique service role name is generated. Use this role to configure identity and access management for AWS. Role generation takes a few minutes. If the role name doesn't appear, refresh the page. [NOTE] -You can configure only one AWS service role per private space. +Each private space supports only one AWS service role. == See Also From 80d9aef3a2ca7627a26b0e372374c6e443514cb6 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 6 Mar 2026 17:50:09 -0300 Subject: [PATCH 2/8] Update cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc --- cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc index 8c443f3d..548e3911 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc @@ -19,7 +19,7 @@ For data transfers that exceed 300 seconds, consider breaking the request into s == Configure HTTP Requests and Read-Response Timeout -When you modify HTTP requests, applications aren't reachable for up to 5 seconds. +When you modify HTTP requests, applications may not be reachable for up to 5 seconds. // SELECT PRIVATE SPACE SHARED include::partial$select-private-space.adoc[tag=selectPrivateSpace] From 8a2eea4da2ed60fd3b9691723494ebf52b863cff Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 6 Mar 2026 17:50:15 -0300 Subject: [PATCH 3/8] Update cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc --- cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc index 548e3911..9f60d69d 100644 --- a/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc +++ b/cloudhub-2/modules/ROOT/pages/ps-config-advanced.adoc @@ -44,7 +44,7 @@ Silently drops HTTP requests. -- . Specify the read response timeout value. + -The default read-response timeout is 300 seconds. Configure this value up to 3600 seconds (1 hour). +The default read-response timeout is 300 seconds. You can configure this value up to 3600 seconds (1 hour). + . Click *Save Changes* or *Discard Changes*. From 86864cd2a5a80ee7dd58e5a508480547000cefd8 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos Date: Fri, 6 Mar 2026 17:59:00 -0300 Subject: [PATCH 4/8] changes --- cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index 7b9ae4a7..c3da2347 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -15,6 +15,7 @@ You can use only asynchronous log appenders. * File appenders, such as FileAppender, RollingFileAppender, AnypointMonitoringFileAppender, and RandomAccessFileAppender, are removed automatically. * When using custom Log4j configurations, both Mule runtime engine and application logs remain available in Runtime Manager. * You can forward tracing module logs using only third-party appenders. You cannot update the logging patterns to send them to Anypoint Monitoring. +* Console logging is disabled by default in CloudHub 2.0. If you change log levels or appenders in a custom `log4j2.xml` and don't see the changes in the logs, ensure that your configuration uses an appender that CloudHub 2.0 collects (for example, a third-party appender that streams to your logging system). Log output from a Console appender alone does not appear in Runtime Manager unless console logging is explicitly enabled for your deployment. You can use any Log4j appender. @@ -23,6 +24,11 @@ https://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSynt == Example: Create a Log4j Configuration Using Splunk +[IMPORTANT] +==== +Console logging is disabled by default in CloudHub 2.0. Changes to log levels or appenders in your custom `log4j2.xml` might not appear in the logs in Runtime Manager if you rely only on a Console appender. To see your custom Log4j configuration take effect, use an appender that streams logs to an external system (such as Splunk) or ensure that log integration is enabled for your deployment so that console output is collected. +==== + For logs to be viewable in CloudHub 2.0 and flow to Splunk, configure the `SplunkHttp` Log4j appender. From 0d6cb7f456822f4d148d614f8f0d53a3b7447720 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 6 Mar 2026 18:03:09 -0300 Subject: [PATCH 5/8] Update cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc --- cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index c3da2347..8089678d 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -15,7 +15,7 @@ You can use only asynchronous log appenders. * File appenders, such as FileAppender, RollingFileAppender, AnypointMonitoringFileAppender, and RandomAccessFileAppender, are removed automatically. * When using custom Log4j configurations, both Mule runtime engine and application logs remain available in Runtime Manager. * You can forward tracing module logs using only third-party appenders. You cannot update the logging patterns to send them to Anypoint Monitoring. -* Console logging is disabled by default in CloudHub 2.0. If you change log levels or appenders in a custom `log4j2.xml` and don't see the changes in the logs, ensure that your configuration uses an appender that CloudHub 2.0 collects (for example, a third-party appender that streams to your logging system). Log output from a Console appender alone does not appear in Runtime Manager unless console logging is explicitly enabled for your deployment. +* Console logging is disabled by default in CloudHub 2.0. If you change log levels or appenders in a custom `log4j2.xml` and don't see the changes in the logs, ensure that your configuration uses an appender that CloudHub 2.0 collects; for example, a third-party appender that streams to your logging system. Log output from a Console appender alone doesn't appear in Runtime Manager unless you explicitly enable console logging for your deployment. You can use any Log4j appender. From 8c8de130a83cb3a4f49c64ac993d50484bb7d35c Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 6 Mar 2026 18:03:15 -0300 Subject: [PATCH 6/8] Update cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc --- cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index 8089678d..0d0e5713 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -26,7 +26,7 @@ https://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSynt [IMPORTANT] ==== -Console logging is disabled by default in CloudHub 2.0. Changes to log levels or appenders in your custom `log4j2.xml` might not appear in the logs in Runtime Manager if you rely only on a Console appender. To see your custom Log4j configuration take effect, use an appender that streams logs to an external system (such as Splunk) or ensure that log integration is enabled for your deployment so that console output is collected. +Console logging is disabled by default in CloudHub 2.0. Changes to log levels or appenders in your custom log4j2.xml might not appear in the logs in Runtime Manager if you rely only on a Console appender. To see your custom Log4j configuration take effect, use an appender that streams logs to an external system, such as Splunk, or enable log integration for your deployment so that console output is collected. ==== For logs to be viewable in CloudHub 2.0 and flow to Splunk, From 58d3dde2bf0ad909617e7932f52696eef51622c5 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 20 Mar 2026 14:28:07 -0300 Subject: [PATCH 7/8] Apply suggestion from @luanamulesoft --- cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index 0d0e5713..d0568919 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -15,7 +15,7 @@ You can use only asynchronous log appenders. * File appenders, such as FileAppender, RollingFileAppender, AnypointMonitoringFileAppender, and RandomAccessFileAppender, are removed automatically. * When using custom Log4j configurations, both Mule runtime engine and application logs remain available in Runtime Manager. * You can forward tracing module logs using only third-party appenders. You cannot update the logging patterns to send them to Anypoint Monitoring. -* Console logging is disabled by default in CloudHub 2.0. If you change log levels or appenders in a custom `log4j2.xml` and don't see the changes in the logs, ensure that your configuration uses an appender that CloudHub 2.0 collects; for example, a third-party appender that streams to your logging system. Log output from a Console appender alone doesn't appear in Runtime Manager unless you explicitly enable console logging for your deployment. +* Console logging is disabled by default in CloudHub 2.0. If you change log levels or appenders in a custom `log4j2.xml` and don't see the changes in the logs, use an appender that CloudHub 2.0 collects, such as a third-party appender that streams to your logging system. Log output from a Console appender alone doesn't appear in Runtime Manager. You can use any Log4j appender. From 493a87ecb09cff33609e2ca608edc0c718f5bfb5 Mon Sep 17 00:00:00 2001 From: Luana Dos Santos <84200607+luanamulesoft@users.noreply.github.com> Date: Fri, 20 Mar 2026 14:28:14 -0300 Subject: [PATCH 8/8] Apply suggestion from @luanamulesoft --- cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc index d0568919..8a794537 100644 --- a/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc +++ b/cloudhub-2/modules/ROOT/pages/ch2-integrate-log-system.adoc @@ -26,7 +26,7 @@ https://logging.apache.org/log4j/2.x/manual/configuration.html#ConfigurationSynt [IMPORTANT] ==== -Console logging is disabled by default in CloudHub 2.0. Changes to log levels or appenders in your custom log4j2.xml might not appear in the logs in Runtime Manager if you rely only on a Console appender. To see your custom Log4j configuration take effect, use an appender that streams logs to an external system, such as Splunk, or enable log integration for your deployment so that console output is collected. +Console logging is disabled by default in CloudHub 2.0. If you rely only on a Console appender, changes to log levels or appenders in your custom log4j2.xml might not appear in the logs in Runtime Manager. To apply your custom Log4j configuration, use an appender that streams logs to an external system, such as Splunk, or enable log integration for your deployment to collect console output. ==== For logs to be viewable in CloudHub 2.0 and flow to Splunk,