What aspect of logging is only possible for Mule applications deployed to customer-hosted Mule runtimes, but NOT for Mule applications deployed to CloudHub?
A.
To change log4j2 log levels in Anypoint Runtime Manager without having to restart the Mule application
B.
To log certain messages to a custom log category
C.
To send Mule application log entries to Splunk
D.
To directly reference one shared and customized log4j2.xml file from multiple Mule applications
Logs and diagnostics are currently available only for applications deployed to CloudHub workers. For applications deployed to a local server, you can send data to external analytics software. See Export Data to External Analytics Tools.
https://docs.mulesoft.com/cloudhub-1/viewing-log-data
A - Log level (info to warn) can be changed without restarting in both on-prem and cloud using runtime manager> settings> logging.
B - Custom log levels can be defined in log4j.xml so possible in both cloud and on-prem envs.
C - Application logs can be redirected to Splunk for both Cloud and on-prem envs.
D - I think it is not even possible on-prem to have a common log4j.xml configuration. Can anyone provide a reference on how to achieve this?
D. To directly reference one shared and customized log4j2.xml file from multiple Mule applications
upvoted 3 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
elagac
1 year, 5 months agoViv2005
1 year, 12 months agomajda091983
2 years agoAK2020
2 years, 1 month agomadgeezer
2 years, 3 months agoAkanshaR91
2 years, 4 months agorodriguescont
2 years, 5 months agoMuleK
2 years, 5 months agoGrump
2 years, 11 months agoPavan_Nagineni
3 years, 3 months ago