Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Tailing Logs on AEM as a Cloud Service | AEM Community Blog Seeding




Tailing Logs on AEM as a Cloud Service by Jetteroheller


In order to monitor or debug AEM environments (or virtually any web environment) one needs data, and that data generally comes from server logs. Adobe’s new AEM as a Cloud Service product, given that it’s entirely a managed web service, does not give you the ability to SSH on to individual containers to view logs, nor does it give you access to any sort of Splunk or Elastic or similar log aggregator.

At this point, to get access to your AEM logs is one of two ways:
1. You can download whole logs out of Cloud Manager, and view them on your local, or
2. You can use the Adobe I/O Cloud Manager CLI to tail logs on any of your AEM as a Cloud Service instances.

Note: there is a current issue with both the Adobe IO CLI as well as Cloud Manager’s log downloads, that large stack traces will currently be truncated, a limitation coming from the internal Splunk integration that the AEM as a Cloud Service infra uses on the back end to aggregate the logs. (The Adobe team uses Splunk themselves at this stage, but the capability hasn’t been added to turn this over to end users).

Read Full Blog

Tailing Logs on AEM as a Cloud Service


Please use this thread to ask the related questions.


Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply


Level 1



Any updated about the truncated stacktrace in log files?
Because it is currently giving an issue to investigate an error further in regarding Adobe Target connection.

So the caused by statement can become handy to provide a solution.