Documentationbreadcrumb arrow Pluginsbreadcrumb arrow AppDynamics data sourcebreadcrumb arrow Troubleshooting
Enterprise Grafana Cloud
Last reviewed: September 2, 2026

Troubleshoot AppDynamics data source issues

This document provides guidance for troubleshooting common issues when configuring and using the AppDynamics data source in Grafana.

License and installation

The AppDynamics data source is an Enterprise plugin. It requires a Grafana Cloud Pro or Advanced plan or an activated Grafana Enterprise license. A missing or invalid Grafana license prevents the plugin from starting. That is a Grafana licensing or catalog problem, not an AppDynamics credential problem.

These errors appear before Grafana sends any request to AppDynamics.

No Install or Enable button

When the plugin isn’t entitled for your Grafana Cloud stack or Grafana Enterprise license, the catalog can hide Install and Enable. A user without the Organization Administrator role also can’t install the plugin.

Symptoms:

  • The AppDynamics plugin page in the catalog shows no Install or Enable button.
  • Installation appears to do nothing.

Solutions:

  1. Confirm that you have the Organization Administrator role. Ask an administrator to install the plugin if you don’t. Refer to Install Grafana Enterprise plugins.
  2. On self-managed Grafana, verify the Enterprise license is valid and includes Enterprise plugins. Refer to Stats and license.
  3. On Grafana Cloud, confirm that your plan is Pro or Advanced and that Enterprise plugins are enabled for your stack. If the button is still missing, contact Grafana Support.

“Plugin health check failed”

This Grafana error means the plugin backend didn’t start. For an Enterprise plugin, the most common cause is a missing or invalid license rather than a problem with your AppDynamics URL or credentials.

Don’t confuse this message with AppDynamics Save & test results such as Data source is working, found N apps. or The configuration setup is incomplete. Those messages appear only after the plugin backend is running.

Symptoms:

  • Save & test, or the plugin catalog, reports Plugin health check failed with no further detail.
  • The data source fails immediately, before Grafana sends any request to AppDynamics.

Solutions:

  1. Confirm that your Grafana Cloud plan is Pro or Advanced, or that self-managed Grafana has a valid Enterprise license.
  2. Review the Grafana server logs for a license error. Refer to “Invalid license for the enterprise plugin”.
  3. If the license is valid, continue with Configuration errors and Authentication errors.

“Invalid license for the enterprise plugin”

This error indicates a Grafana licensing problem, not an AppDynamics credential problem. The Enterprise license token is missing, malformed, or truncated, so the plugin can’t validate its entitlement.

Symptoms:

  • The Grafana server log contains an error similar to invalid license for the enterprise plugin.
  • The plugin fails to start, and Save & test returns Plugin health check failed.

Solutions:

  1. On self-managed Grafana, confirm that you installed a valid Grafana Enterprise license. The token is a JSON Web Token (JWT) with three parts separated by periods. If you provide the license through the GF_ENTERPRISE_LICENSE_TEXT environment variable or a license file, copy the full token with no truncation or extra whitespace.
  2. After you update the license, restart Grafana and try again.
  3. On Grafana Cloud, contact Grafana Support to confirm that your Pro or Advanced plan includes the AppDynamics plugin. Don’t apply a license JWT to Grafana Cloud yourself.

Plugin version

Confirm you’re on a recent plugin version before investigating AppDynamics credentials or query syntax. Many query-editor and template-variable issues are already fixed in current 3.12.x releases. This data source requires Grafana 11.6.7 or later.

  1. Click Administration > Plugins and data > Plugins in the left-side menu.
  2. Search for AppDynamics and open the plugin page.
  3. Compare the installed version with the latest available version.
  4. On self-managed Grafana, click Update if a newer version is available. Refer to Plugin management.

Note

On Grafana Cloud, plugins update automatically. In other managed environments, the platform provider may lag behind the latest release, so confirm which version you’re running.

If template variables don’t interpolate or a drop-down shows $undefined after you update, refer to Template variable errors.

Verify the connection

After the plugin is installed, licensed, and up to date, verify that the AppDynamics connection health check passes:

  1. Click Connections in the left-side menu.
  2. Click Data sources and select your AppDynamics data source.
  3. Click Save & test.
  4. Confirm you see the success message: Data source is working, found N apps.

If Save & test returns Plugin health check failed, start with License and installation. For AppDynamics-specific messages, start with Configuration errors, Authentication errors, or Connection errors.

Configuration errors

Configuration errors occur when required fields are missing or incomplete.

“The configuration setup is incomplete”

This error indicates that one or more required configuration fields are missing.

Possible causes:

  • No URL configured
  • No credentials configured (neither basic authentication nor API client)
  • Partial API client credentials (missing client name, domain, or secret)
  • Partial basic authentication (missing username or password)

Solutions:

  1. Verify the URL field contains your AppDynamics controller URL, for example https://mycompany.saas.appdynamics.com.
  2. Ensure all required credential fields are filled:
    • For basic authentication: User and Password
    • For API client authentication: Client Name, Client Domain, and Client Secret
  3. Click Save & test to verify the configuration.

Authentication errors

Authentication errors occur when there are issues with your credentials, permissions, or token handling.

“The credentials are incorrect” or “Unauthorized (401)”

The full error from the plugin is: The credentials are incorrect. Check that the API key, or username and password, are correct. The error is prefixed with Metrics or Analytics to indicate which API failed.

Possible causes:

  • Incorrect username or password
  • Invalid API client secret
  • Wrong client name or domain
  • Insufficient permissions
    • For an Analytics error, the Analytics API key is missing the Manage Schema permission. The connection test calls the /events/schema endpoint, which requires this permission.

Solutions:

  1. Verify the credentials match what is configured in the AppDynamics Administration settings.
  2. For API client authentication, verify the Client Name matches the API client name in AppDynamics, and the Client Domain matches your company name from the controller URL.
  3. Regenerate the client secret in the AppDynamics Controller UI if needed and update the data source configuration.
  4. Ensure the user or API client role has view access to Account, Applications, Databases, and Analytics.
  5. For an Analytics error, verify the Analytics API key has both the Manage Schema and Query Custom Events permissions under Custom Analytics Events. Because API key permissions can’t be changed after creation, create a new key with both permissions if either is missing.

“Token has expired”

This error indicates that the OAuth token used for API client authentication has expired.

Possible causes:

  • API client secret has been rotated
  • API client has been deleted or deactivated
  • Token refresh failed

Solutions:

  1. Regenerate the client secret in the AppDynamics Controller UI.
  2. Update the Client Secret in the Grafana data source configuration.
  3. Click Save & test to verify the new credentials work.
  4. If the issue persists, verify the API client is still active in AppDynamics and has the correct role assigned.

“Empty auth token received” or “No authentication response received”

The AppDynamics controller returned an empty or missing authentication token.

Possible causes:

  • API client credentials are incorrect
  • The AppDynamics controller rejected the token request
  • Network issues interrupted the authentication handshake

Solutions:

  1. Verify the Client Name, Client Domain, and Client Secret are correct.
  2. Check that the API client is active and has the correct role assigned in AppDynamics.
  3. Verify network connectivity from the Grafana server to the AppDynamics controller.
  4. Click Save & test to retry authentication.

Connection errors

Connection errors occur when Grafana can’t reach the AppDynamics controller or Analytics endpoint.

“Could not connect to AppDynamics”

The full error from the plugin is: Could not connect to AppDynamics. This usually happens when the URL is incorrect.

Possible causes:

  • Incorrect URL format
  • Extra path in the URL (such as /controller)
  • Network connectivity issues

Solutions:

  1. Verify the URL format is correct: https://<COMPANY>.saas.appdynamics.com.
  2. Ensure the URL doesn’t include a trailing path like /controller.
  3. Test network connectivity from the Grafana server to the AppDynamics controller.
  4. Check that firewall rules allow outbound HTTPS (port 443).

Connection timeout or “no response received from AppDynamics”

The connection to AppDynamics took too long to establish.

Possible causes:

  • Network connectivity issues
  • Firewall blocking the connection
  • AppDynamics service is experiencing issues

Solutions:

  1. Verify network connectivity from the Grafana server to AppDynamics.
  2. Ensure your firewall allows outbound connections to your AppDynamics controller on port 443.
  3. If using Private data source connect (PDC), verify the PDC agent is running and connected. For more information, refer to Private data source connect (PDC).
  4. If timeouts occur only for certain queries, try narrowing the time range to reduce data volume.

Query errors

Query errors occur when executing queries against the Metrics or Analytics APIs.

“empty metric query”

No metric has been selected in the query editor.

Solutions:

  1. Ensure you’ve selected an Application in the query editor.
  2. Select a Metric path from the available metrics.

“HTML response received from data source API”

The AppDynamics controller returned an error page instead of JSON data.

Possible causes:

  • Incorrect URL
  • AppDynamics controller is down or experiencing issues
  • The selected application or metric no longer exists

Solutions:

  1. Verify the URL in the data source configuration is correct.
  2. Check that the AppDynamics controller is running and accessible.
  3. Ensure the selected application and metric path still exist in AppDynamics.

“(500) error parsing query, or error with no additional context received” (Analytics)

An Analytics (ADQL) query has a syntax error or references invalid data. AppDynamics returns HTTP 500 errors for query parsing failures without detailed error context.

Possible causes:

  • ADQL syntax error (missing keyword, unmatched quotes, invalid function)
  • Invalid table or field name in the query
  • Analytics API is unavailable

Solutions:

  1. Verify your ADQL syntax. Refer to the ADQL documentation.
  2. Check that table and field names in the query are correct and exist in your Analytics schema. Use the autocomplete feature in the query editor to verify available tables and fields.
  3. Simplify the query to isolate the syntax issue (for example, start with SELECT count(*) FROM transactions).
  4. Verify the Analytics API connection by clicking Save & test in the data source settings.

“Number of intervals in aggregation is too large”

The query time range is too wide for the selected aggregation interval.

Solutions:

  1. Narrow the dashboard time range to reduce the number of data points.
  2. Increase the aggregation interval in your query.
  3. Break the query into smaller time windows.

“Event type does not exist for account [X] and event type [Y]”

An Analytics query references a table or event type that doesn’t exist or isn’t accessible for the configured account.

Possible causes:

  • AppDynamics Analytics license doesn’t cover the requested data
  • The table hasn’t been created yet
  • Incorrect Global Account Name in the data source configuration
  • The event type name is misspelled in the ADQL query

Solutions:

  1. Verify that the table name in your ADQL query (for example, transactions, browser_records) is correct.
  2. Check that the Global Account Name in the data source configuration matches your account. You can find it in the AppDynamics Controller UI under Settings > License > Account.
  3. Verify that your AppDynamics Analytics license covers the data you’re trying to query.
  4. Ensure data has been pushed to the table or event type you’re querying.

“invalid/empty analytics query received”

The Analytics query field is empty.

Solutions:

  1. Enter a valid ADQL query in the query editor. For example: SELECT count(*) FROM transactions.

No data returned

Your query executes without error but returns no results.

Possible causes:

  • The time range filter excludes all data
  • Wrong application or metric selected
  • The user or API client lacks view access to the specific application

Solutions:

  1. Expand the Grafana time range to verify data exists.
  2. Verify you’ve selected the correct application and metric path.
  3. Check that the user or API client has view access to the application in AppDynamics.

Template variable errors

These errors occur when using template variables with the data source. On plugin versions earlier than 3.11.17, update to 3.12 or later before you change variable queries. Refer to Plugin version.

Variables don’t interpolate or the application list is empty

On plugin versions earlier than 3.11.17, template variables in the Metrics Application field and in Health, Events, Tiers, and Metric Names inputs might not interpolate. The application drop-down for those query types can also appear empty.

Solutions:

  1. Update the plugin to 3.12 or later. Version 3.11.11 fixed query-editor interpolation. Version 3.11.17 fixed template variables in the Metrics Application field. Refer to Plugin version.
  2. If the application list is still empty after you update, click Save & test on the data source. Then continue with Authentication errors.

$undefined in a drop-down

The Health, Events, Tiers, and Metric Names application_id fields list AppDynamics applications (name and ID). They don’t list dashboard variables. If the field shows $undefined, or your variable isn’t in the list, Grafana didn’t store the variable name.

Solutions:

  1. Type ${variableName} as a custom value. For example, type ${application} rather than selecting a numeric application ID.
  2. Refer to AppDynamics template variables for supported patterns.

Variables return no values

Possible causes:

  • Data source connection is not working
  • Variable query doesn’t match a supported pattern
  • Parent variables (for cascading variables) don’t have valid selections

Solutions:

  1. Verify the data source connection is working by clicking Save & test in the data source settings.
  2. Check that the variable query matches a supported pattern (for example, Applications, AppName.Tiers). Refer to the template variables documentation for supported patterns.
  3. For cascading variables, ensure parent variables have valid selections.
  4. Verify the identity has permissions to list the requested resources.

“Templating must be one of Applications, AppName.BusinessTransactions, AppName.Tiers, AppName.Nodes, AppName.Path”

The variable query uses an unsupported pattern.

Possible causes:

  • Misspelled query keyword (for example, Tier instead of Tiers)
  • Missing application name before the . separator
  • Invalid query format

Solutions:

  1. Verify the query matches one of the supported patterns exactly. Supported patterns are case-sensitive.
  2. For application-specific queries, ensure the application name or variable precedes the . (for example, MyApp.Tiers, not just Tiers).
  3. Refer to the template variables documentation for the complete list of supported patterns and examples.

“The value after ‘.’ must be BusinessTransactions, Tiers or Nodes”

The part of the variable query after the application name isn’t a supported type.

Possible causes:

  • The keyword after the first . isn’t BusinessTransactions, Tiers, Nodes, or Path
  • Extra or missing segments in the query

Solutions:

  1. Use one of AppName.BusinessTransactions, AppName.Tiers, AppName.Nodes, or AppName.Path....
  2. To scope business transactions or nodes to a tier, use AppName.TierName.BusinessTransactions or AppName.TierName.Nodes.
  3. Refer to the template variables documentation for the complete list of supported patterns.

Multi-value variables replace values with * in Metrics

This is expected behavior. Multi-value variables aren’t supported in Metrics queries. If multi-value variables are found in a metric path, they’re replaced with *, which matches all values.

To use multi-value variables, use an Analytics (ADQL) query instead:

SQL 
SELECT distinct(transactionName), count(*) FROM transactions WHERE transactionName IN (${transactionName:doublequote})

Enable debug logging

Use these techniques to gather more information when diagnosing issues.

Enable query inspector

To view the executed query and response:

  1. Open your dashboard panel.
  2. Click the panel title and select Inspect > Query.
  3. Review the request and response for error details.

Check Grafana server logs

For detailed error information:

  1. Access your Grafana server logs.
  2. Search for appdynamics to find relevant log entries.
  3. Look for error messages and stack traces that provide more context.

To enable debug-level logging:

  1. Set the Grafana log level to debug in the configuration file:

    ini 
    [log]
level = debug

  2. Review logs in /var/log/grafana/grafana.log (or your configured log location).

  3. Reset the log level to info after troubleshooting to avoid excessive log volume.

Get additional help

If you continue to experience issues after following this troubleshooting guide:

  1. Check the AppDynamics documentation for platform-specific guidance.

  2. Review the Grafana community forums for similar issues.

  3. Contact Grafana Support if you’re a Grafana Enterprise, Cloud Pro, or Cloud Advanced user.

  4. When reporting issues, include:

    • Grafana version and plugin version
    • Authentication method (basic authentication or API client)
    • Error messages (redact sensitive information like tokens and passwords)
    • Steps to reproduce
    • Relevant configuration (redact credentials)