Known Issues

A list of known issues for Splunk AppDynamics Controller.

Key Product Summary Affected Version(s) Fix Available In
CON-9335 Controller

Business transaction registration fails because a write operation is routed through a read-only database connection.

Workaround: Set the cluster/global configuration appdynamics.read.only.thread.disabled=true.

26.7.0 -
CON-9457 Controller Role-permission audit entries omit Analytics Search object names, making audit records insufficient for compliance and troubleshooting. No workaround available. 26.4.4 -
CON-9502 Controller

Machine Agents running with SIM deactivated can incorrectly display 0% uptime even when they are reporting normally.

Workaround: Verify reporting through the Agent > Machine > Availability metric or Metric Browser instead of relying on the displayed uptime.

26.4.0 -
CON-9114 Controller

The consistency checker incorrectly reconciles intentionally excluded Kubernetes SIM entities. This increases database load and row-lock waits and degrades stale-pod purging.

Workaround: Disable controller.mds.data.consistency.checker.enabled.

26.1.3 -
CON-8537 Controller

After an RDS upgrade or failover, stale MDS connections can exhaust the pool and degrade services or leave the Controller unavailable.

Workaround: Restart the Controller after RDS maintenance or failover to recreate the database connection pool.

25.10.0 -
CON-9044 Controller Entity Liveness historical loading can time out or return HTTP 504 at scale, leaving liveness filters unavailable. No workaround available. On-prem 26.1.3 -
IAM-7355 Accounts
When you navigate to Settings > Administration > Authentication Provider > SAML Group Mappings and perform the following actions in the Mapping of Group to Roles
  • Add a new group and assign a role. Save both the popup and the main page.
  • Edit an existing group and update the group name by changing only the letter case. For example, changing "TEST_NAME_3" to "TEST_NAMe_3", then save the changes.

AppDynamics does not retain the edited SAML group if the update involves only letter case changes. After saving, the group is removed from the mapping list, and all associated role mappings are lost.

Workaround:

To update a group name with only a case change:
  1. Delete the existing group-to-role mapping for the group you wish to modify.
  2. Add a new group-to-role mapping using the desired case for the group name.
  3. Reassign the roles that were previously mapped to this group.
Note: This issue is specific to group name changes involving letter case only. Renaming a group entirely does not trigger the issue.
25.10.0, 26.1.0, 26.4.0, 26.7.0 -
DBMON-11927 Database Monitoring

Database Monitoring has these ADQL-related issues:

  • A five-minute time range contains only four data points, and data for the first minute is missing.

  • Wait-state data is unavailable for time ranges of three months or longer.

  • Plan cache data is unavailable when the ADQL cacheplanquerylist query fails.

26.1.0, 26.4.0, 26.7.0 -
DBMON-11926 Database Monitoring

When you select the MSSQL database file tab, data does not load because the request supplies a dbServerId value of 0.

Workaround: Perform a hard refresh of the page to load the data.

26.4.0, 26.7.0 -