Skip to content

AEM –Changing Log Levels


If you require any more information or have any questions about our site’s disclaimer, please feel free to contact us by email at [email protected]

All the information on this website – – is published in good faith and for general information purpose only. SKYDEVOPS does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this website (skydevops), is strictly at your own risk.
SKYDEVOPS will not be liable for any losses and/or damages in connection with the use of our website.

From our website, you can visit other websites by following hyperlinks to such external sites. While we strive to provide only quality links to useful and ethical websites, we have no control over the content and nature of these sites. These links to other websites do not imply a recommendation for all the content found on these sites. Site owners and content may change without notice and may occur before we have the opportunity to remove a link which may have gone ‘bad’.

Please be also aware that when you leave our website, other sites may have different privacy policies and terms which are beyond our control. Please be sure to check the Privacy Policies of these sites as well as their “Terms of Service” before engaging in any business or uploading any information.


By using our website, you hereby consent to our disclaimer and agree to its terms.


Should we update, amend or make any changes to this document, those changes will be prominently posted here.

-== & ==-


Changing the Logging level in AEM for many reasons, this guide will give you basic overview of how to change the LOG Level in AEM. Some of the parameters which can be tweaked are mentioned below. No restart required.

  • Log Level and Log File, to define the location and log level of the central logging configuration (error.log). The level can be set to one of DEBUGINFOWARNERROR and FATAL.
  • Number of Log Files and Log File Threshold to define the size and version rotation of the log file.
  • Message Pattern defines the format of the log messages.


STEP-01: Go to AEM OSGI configuration Manager, or directly navigate to slinglog to check the different log configurations.


STEP-02: Click on the wrench icon to edit the respective log configuration, for example error.log, which will take you to edit the sling logging configuration for error.log


STEP-03: Select the appropriate logging level and SAVE the configuration


STEP-04: Verify the logging level has been changed by checking the error log





Shashi View All

A passionate devops and automation engineer

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: