Skip to content
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

W-15973244-disable-customlog4j-kt #1370

Open
wants to merge 3 commits into
base: v2.8
Choose a base branch
from
Open

W-15973244-disable-customlog4j-kt #1370

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e38ea91
W-15973244-disable-customlog4j-kt
kevintroller Nov 22, 2024
f966448
Update modules/ROOT/pages/use-log4j-appender.adoc
kevintroller Nov 22, 2024
20c49ec
Merge branch 'v2.8' into W-15973244-disable-customlog4j-kt
kevintroller Nov 22, 2024
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
17 changes: 16 additions & 1 deletion modules/ROOT/pages/use-log4j-appender.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,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 Anypoint Monitoring.

== Enabling Log4j
== Enable Log4j

Custom Log4j configurations are disabled by default. When you install Runtime Fabric, the parameter is disabled (`false`) in `Values.yaml`. You must set the value to `true`.

Expand Down Expand Up @@ -96,6 +96,21 @@ For the latest version of Splunk, see https://github.com/splunk/splunk-library-j

After your application starts, logs start flowing to your custom Log4j appender, and you can view them on your target logging system.

== Disable Custom Log4j

If you enabled Custom Log4j in the `values.yaml` during the installation of Runtime Fabric and you want to disable it at the Runtime Fabric cluster level, follow these steps:

. In your cluster, run:
+
----
# kubectl -nrtf patch secret custom-properties -p '{"data":{"CUSTOM_LOG4J_ENABLED":""}}
----
. Restart the Runtime Fabric agent pod:
----
# kubectl delete pod -n rtf -l app=agent
----
. Restart the Mule app associated with the custom Log4j configuration.

== See Also

* xref:mule-runtime::logging-mdc.adoc[MDC Logging]