Trace AEM Bundle Issues

There comes a point where you need to triage why a bundle isn't behaving as you would expect. The simplest way I've found is to setup a logger. A logger has many advantages over tailing logs/error.log...

• You can target a specific bundle. No need to grep.
• You can leave the generic logger on something less frequent like 'Information'.
• This is likely what you'll be sending if you end up talking to Adobe support.

On to setting up a logger for a specific bundle...

1. Open Console: http://localhost:4502/system/console/configMgr
2. Find the bundle PID you want to trace. In our case, we want to trace com.adobe.granite.auth.saml
3. Add a new Logger entry at "Apache Sling Logging Logger"
   • Set the Log Level: Trace
   • Set the Log File Location: logs/saml-error.log
   • Specify your Bundle PID: com.adobe.granite.auth.saml
4. Go tail it via terminal: tail -f logs/saml-error.log