The Kubernetes® events are automatically generated when the entities change state, errors occur, and so on. The Cisco AppDynamics Infrastructure Collector collects events from your Kubernetes microservices/applications and you can observe the event severity with the details on the Cisco Cloud Observability UI. To modify the default event configuration, see Configure Events.

The events collection helps you troubleshoot the issues related to entities. See Kubernetes documentation.

This document contains references to Kubernetes®  documentation. Cisco AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.

Points to Consider

To view the events on the entities page, ensure that you:

  • Download the latest Helm chart.
  • Use the same collectors-values.yaml file that you used during the installation. This document uses collectors-values.yaml file.

Supported Entities

You can observe the Kubernetes events for these entities:

  • Clusters
  • Namespaces
  • Workloads
  • Pods
  • Persistent Volume Claim
  • Configurations
  • Hosts (only those that have a corresponding node)

Troubleshoot Issues with Entities Using Event Collection

To troubleshoot the issue using event collection:

  1. Monitor Health of Entities
  2. Observe Kubernetes Events
  3. Explore Logs

Example: Consider a scenario where you observe that your cluster is unhealthy, you would want to understand the root cause and troubleshoot the issue that is causing the cluster to be unhealthy.

  1. Monitor the health of the cluster:
    1. On the Relationships pane, click the red symbol under Cluster.
    2. Select the cluster from the list view.
    3. On the details view page, click the drop down next to Health Violations.
      This shows the health rule violation in red for a specific time range. 
  2. Observe Kubernetes events:
    1. Click the same time range in the Kubernetes Events histogram.
      This shows the count and severity of the events namely warning or severe.
    2. Click View Event Summary.
      This shows the summary that includes event reason and the entities that are affected. This helps you find out which event might be causing the issue.
    3. To check whether all time ranges show the same event reason or what are the top event reasons, click All Time Ranges.
      This helps to analyze what events are generated during the specified time range that caused the cluster to be unhealthy.
  3. Troubleshoot with logs:
    1. Check Logs to understand what is causing a specific event in a specific time range by using the histogram.
      This shows what error was shown for the same time range on the application or microservices.

Next Steps

See the following pages to help you more precisely monitor your events:

  1. Configure Events
  2. Observe Kubernetes Events


OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.