Skip to main content
Connect your AppDynamics (Cisco) APM platform to enable CloudThinker agents to list applications, tiers, nodes, and business transactions, pull performance metrics, and review active health-rule violations and error events across your monitored environment. AppDynamics authenticates with an API client (OAuth2 client credentials) scoped to a Controller account. The connection is read-only — agents query the Controller REST API but never mutate AppDynamics resources.

Prerequisites

  • An AppDynamics Controller (SaaS or on-premises) with the applications you want to monitor.
  • An API client created under your account, with its Client Name and Client Secret.
  • Your Controller URL and account name.
Grant the API client a read-only role. CloudThinker only reads application health, metrics, violations, and events — it never modifies AppDynamics configuration.

Setup

1

Open the AppDynamics Controller

Sign in to your AppDynamics Controller as an administrator. Your Controller URL follows the format https://<account>.saas.appdynamics.com for SaaS, or your on-premises host.
2

Create an API client

Go to Settings → Administration → API Clients and click Create:
  • Client Name: cloudthinker
  • Description: Read-only access for CloudThinker agents
  • Roles: assign a read-only role with access to the applications you want CloudThinker to monitor
Copy the generated Client Secret immediately — it is shown only once.
3

Find your account name

Your account name appears under Settings → License or as the subdomain of your Controller URL (e.g. myaccount in https://myaccount.saas.appdynamics.com).
4

Add the connection in CloudThinker

Navigate to Connections → AppDynamics and enter:
  • Controller URL: your Controller base URL
  • Account Name: your AppDynamics account name
  • Client Name: the API client name (e.g. cloudthinker@myaccount)
  • Client Secret: the secret you copied
Click Connect. CloudThinker verifies the credentials and shows a Connected status.
Copy the Client Secret immediately after creating the API client. AppDynamics shows it only once — if it’s lost, you’ll need to regenerate the secret.

Connection details

All four fields are required together — AppDynamics OAuth2 client-credentials authentication needs the Controller URL, account, client name, and secret to obtain an access token.

Required permissions

Assign the API client a read-only role with access to the applications CloudThinker should monitor. Read access covers applications, tiers, nodes, business transactions, metrics, health-rule violations, and events.
Follow least privilege: a read-only role is enough for monitoring and triage. Keep configuration and administration permissions off the client CloudThinker uses.

Agent capabilities

Once connected, agents have read access to your AppDynamics APM data.

Verify the connection

Example prompts

For large environments, scope requests to a named application and a short time window so the agent returns focused results.

Troubleshooting

The client name or secret is wrong, or the API client lacks the required role. Verify the Client Name and Client Secret, confirm the client has a read-only role assigned, and reconnect.
The Controller URL is unreachable from CloudThinker. Verify the Controller URL is correct and accessible, and that on-premises Controllers allow inbound connections.
The account name doesn’t match the Controller. Check Settings → License or your Controller subdomain and update APPD_ACCOUNT_NAME.
The API client’s role has no access to the applications, or the account has no matching data. Confirm the role grants read access to the target applications, then retry with a known application name.
Unbounded application or metric queries return too much data. Scope requests to a named application and a short time window so results stay focused.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • HTTPS Controller URL — always use an HTTPS Controller URL to protect credentials in transit.
  • Dedicated API client — create a client used only by CloudThinker so you can revoke it independently without affecting other integrations.

Datadog Connection

APM, metrics, and monitoring

SigNoz Connection

Traces, metrics, and logs in one place