DocumentationExperience Cloud KCS

Change logger level of a custom log file to INFO in Adobe Experience Manager

Last update: September 1, 2026

This article explains how to change the logger level for a custom log file, such as pco.log, to INFO on Adobe Experience Manager (AEM) production publisher instances. Custom log files are managed through Sling Logger configurations. Adjusting the logger level to INFO can be useful for troubleshooting or monitoring, but it may increase disk and memory usage due to more verbose logging. Monitor system resources after making this change to avoid performance issues or service interruptions caused by excessive log-file growth.

Description description

Environment

  • Adobe Experience Manager 6.5
  • Self-managed or on-premises production publisher instances

Issue/Symptoms

  • Need to increase logging detail for a custom log file, such as pco.log, on production publisher instances.
  • Concern about increased resource usage and disk space consumption.

Cause

Setting the logger level to INFO increases the amount of information written to the log file, which can lead to higher disk and memory usage if not monitored.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Log in to the AEM Web Console on each production publisher instance.
  2. Navigate to OSGi > Configuration, typically available at /system/console/configMgr.
  3. In the list of configurations, look for the Sling Logger configuration associated with the custom log file. The configuration name may reference the log file name or the logger category used for this custom log.
  4. If multiple logger configurations exist, identify the correct one by checking the Log File or Log Output field for the entry that points to the custom log file.
  5. Edit the identified configuration and set the Log Level to INFO.
  6. Save the configuration.
  7. Verify that the log file is recording entries at the INFO level by reviewing recent log entries.
  8. Monitor disk usage on the publisher instances to ensure that increased log volume does not exhaust available storage.
recommendation-more-help
experience-cloud-kcs-help-kbarticles