specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: AppDynamics
providerId: appdynamics
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Rate Limiting
  - APM
  - Observability
description: AppDynamics does not publish hard per-second rate-limit numbers for its Controller REST API
  or Metric & Snapshot API. Throughput is governed by the Controller's overall capacity (sized by edition
  and CPU/memory) and by per-account fairness throttling on SaaS Controllers. The Cisco AppDynamics Cloud
  Native (formerly AppDynamics Cloud) APIs follow Cisco's standard observability platform throttling.
  Heavy automation against the Controller REST API should batch requests, prefer the Metric & Snapshot
  API for time-series, and respect 429/503 responses with backoff.
notes: No public numeric rate-limit table is documented; values are environment-sized.
sources:
  - https://docs.appdynamics.com/
  - https://www.splunk.com/en_us/products/pricing/observability.html
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Controller REST API
    scope: account/controller
    metric: varies
    limit: see Controller capacity sizing
    notes: Sized by Controller edition and infrastructure; SaaS Controllers apply per-account fairness
      throttling.
  - name: Metric and Snapshot API
    scope: account/controller
    metric: varies
    limit: see Controller capacity sizing
    notes: Heavy time-series queries can be throttled to protect shared Controller capacity.
  - name: Events Service / Analytics Events API
    scope: account/region
    metric: varies
    limit: see service-specific quotas
    notes: Event ingestion sized by Events Service capacity in the customer's region.
policies:
  - name: Backoff Strategy
    description: Implement exponential backoff with jitter; honor 429 / 503 responses with retries spaced
      across multiple seconds.
  - name: Batch and Aggregate
    description: Use Metric & Snapshot API for time-series rather than per-call REST polls; batch event
      submissions.
  - name: Capacity Sizing
    description: Throughput depends on Controller sizing (vCPU and edition); engage AppDynamics support
      to right-size if API automation pressures the Controller.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com