This page includes details about storing and managing logs for pods on-premises and on SaaS.

By default, the Cluster Agent collects logs for restarted or failed pods. The pod failure logs capture the status of the CrashLoopBackoff events that display the Back-off restarting failed container message. This message usually indicates that Kubernetes started a container but then the container quickly exits. If this happens, Kubernetes keeps trying to restart the container. These log messages can help you determine why the pod is exiting, whether due to a liveness probe, or some other issue.

Before You Begin

The minimum requirement for the agent version is 20.7 and the Controller version is 20.10.0.

You can store the logs when the following requirements are met:


  • Enable logging by using the Cluster Agent configuration setting, sim.cluster.logs.capture.enabled.
  • Update the full file path to store the logs using the Controller setting, sim.cluster.logs.root.file.path.
    The logs are stored in the specified file location.

  • Ensure to have 50 GB hard disk space on the filesystem.
  • When updating the file path, ensure to move previously collected logs from the old path to the new path to view them on the Controller UI.


For SaaS, create an AppDynamics Support ticket to enable the manage logs feature for your account.

Configure Logs for On-Premises

For SaaS, the Technical Support team updates the configuration properties. Therefore, to configure the logs for SaaS, contact the support team by creating an AppDynamics Support ticket.

The following table lists the log settings required for an on-premises environment:


The folder name to store the pod logs.

Controller Administration Console with root user permission (Controller Settings)



An option to enable or disable log capturing.

This option is disabled by default.

Controller Administration Console with root user permission

You can configure this setting at both account level (Account Settings) and Controller level (Controller Settings)


The number of days after which the logs get cleared from the storage.Controller Administration Console with root user permission (Controller Settings)10


The complete root file path to store the logs.
Modifying the path results in storing the logs in the new path but the older logs will remain in the older location.
Controller Administration Console with root user permission (Controller Settings)/opt/appdynamics

View Logs

You can view the logs on the Pod Details page and the Cluster Event page.

Pod Details Page

  1. Select Servers > Clusters > Cluster Name.
  2. Select a Cluster Agent and double-click. The cluster interface displays the Dashboard, the Pods, the Inventory, and the Events tabs.
  3. Click Pods.
  4. Double-click any pod to display its Pod Details panel
  5. Review the Error Log.
    Error Log on Pod Details page includes timestamp and status of log trigger
  6.  Click the Actions icon to view the log details.
    The details of the error log is displayed along with timestamp and the log trigger status

Cluster Events Page

  1. Click the Servers tab.
  2. On the left navigation bar, select Events to see a list of events that have been reported from both servers and clusters.
    Select Clusters > <Clustername> > Details > Events
  3. Double-click a cluster event to view the logs under the Logs tab.
    Cluster Event Logs tab includes the log details