This page covers common issues and troubleshooting for Application Performance Monitoring.

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

Docker Image Download Fails With 429 Too Many Requests

If downloading any Cisco Cloud Observability Docker image fails with a 429 Too Many Requests response code, you may have exceeded your download rate limit in Docker Hub. This issue automatically resolves itself when your rate limit resets. For more information on the rate limit for different account types, see Download rate limit.

Splunk AppDynamics recommends using a paid Docker subscription account to prevent rate limit issues.

As a workaround, you can store the Docker image in your own registry. Use the following configuration options in your collectors-values.yaml file to set the image URL:

  1. appdynamics-cloud-k8s-monitoring.logCollectorPod.env
  2. appdynamics-cloud-k8s-monitoring.clustermonPod.image
  3. appdynamics-cloud-k8s-monitoring.inframonPod.image

Traces Ingestion Request Failed Due To Content Length Exceeded

If your trace packets are getting dropped, this error indicates that the size of the trace packet is greater than the allowed limit. The allowed limit is 1 MB. To resolve this issue you must reduce the batch size (the default is 1000) and re-install the collector. Modify the collector-values.yaml file and add the following configuration. Uninstall and install the collector again:

appdynamics-otel-collector:
  configOverride:
    batch/traces:
      send_batch_size: 750
      timeout: 10s
      send_batch_max_size: 750
CODE

If the issue is still not resolved, lower the batch size number below 750. 

Attributes Exceeded the Allowed Length 

If some attribute values are large and the packet size exceeds beyond 1 MB, apply a truncate processor. The following example will truncate the attributes values to 128 characters. Add the following configuration in the collector-values.yaml file. Uninstall and install the collector again:

configOverride:
  processors:
    transform/truncate:
      error_mode: ignore
      trace_statements:
        - context: span
          statements:
            - truncate_all(attributes, 128)
        - context: spanevent
          statements:
            - truncate_all(attributes, 128)
  service:
    pipelines:
      traces:
        processors: [memory_limiter, k8sattributes, transform/truncate, batch/traces]
CODE

To exclude certain metrics or apply a filter to fetch less data, see Transform Processor and Filter Processor.

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