Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
When configuring an AppDynamics Java Agent on a Tomcat server with Felix framework, some users ran into the following error message: java.lang.NoClassDefFoundError: com/singularity/ee/agent/appagent/entrypoint/bciengine/FastMethodInterceptorDeleg...
Question How do I instrument Apache Tomcat on CA Project Portfolio Management (Clarity PPM)? Solution Launch the NSA console Navigate to CSA properties -> Application tabUnder "Application Server" select Apache Tomcat as the vendor and edit the Ja...
As seen in the CometD Support documentation, POJO transactions are identified out of the box on CometD applications. The business transactions are identified and split based on the channel names. In some scenarios, this may lead to business transact...
Question: Injecting special headers into an application payload is disturbing application functionality. How do I resolve this? Answer: Disable the exit call correlation based on the exit call that is being sent to the payload. There are two wa...
Problem Users with on-premise Controllers using Java Machine Agents report that no hardware metrics are showing on the Controller UI. To troubleshoot this issue, review the Machine Agent logs. The following error message indicates that the Agent...
To set up a Java Agent to automatically give unique names to nodes for the application, add the following element to the /conf/controller-info.xml file. <auto-naming>true</auto-naming> Example using a 4.2.14.0 Agent: Add the following e...
The Java Agent has been configured on an IBM Server and the following error messages are appearing in the application log files: ERROR UserInterface Displaying to the user an exception message that is not a UserDisplayableException java.lang.Ver...
When running WebSphere with Security Enabled, the user must provide permissions to the Java Agent, to ensure a seamless interaction between the two. Add the following snippet to the security policy file: grant codeBase "file:\* AGENT_DEPLOYMENT_...
Problem: Users find JNI-related warning messages in application logs. Example: WARNING: JNI local refs: 76306, exceeds capacity: 32 at sun.instrument.InstrumentationImpl.getAllLoadedClasses0(Native Method) at sun.instrument.InstrumentationI...
Users with applications using a java.util.concurrent.Future package while making asynchronous calls can track their async call activity as follows: Open the Application Agent config file located at <agent-install-dir>\ver4.x.x.x\conf\app-agent-con...
Problem: All Java Agents under the application have been registered successfully, but are reporting status as down. From the Agent logs: log file Solution: First, check if the Agents have been disabled? In the Controller UI, click on the A...
This article describes how to configure the AppDynamics Java Agent for TIBCO Business Works. Common Configuration and Deployment Scenarios The two most common ways to add the Java Agent to the TIBCO BusinessWorks process are: Configure and deploy us...
Question Why is the Java Agent reporting a large number of com.singularity.ReflectionError messages? Is there a negative impact of these errors on the Agent? Answer The Java Agent uses a Reflection API at runtime to find class information. D...
Scenario: A legacy Machine Agent and Java Application Agent are installed on a machine. Despite correct installation and configuration, one or both of the Agents do not report. The first step in troubleshooting this issue is to validate the Unique ...
What do I need to know about configuring multiple Java Agent JVMs that reside on a single machine? This article describes how to configure multiple JVMs for the AppDynamics Java Agent when they reside on a single machine. In the AppDynamics model...
If the path (including name) of the agent truststore is specified using the <controller-keystore-filename> element in the agent configuration file controller-info.xmlthen agent loads that trustore.If not specified in thecontroller-info.xml, the Ja...
Finding the load average calculated by a Java Agent on a Windows server requires the following data: ProcessorQueueLength counts how many threads are ready in the processor queue, but not currently able to use the processor. To find this value, la...
Problem You want to capture a heap dump of a Java process on Windows. You launch a command prompt with admin privileges and use "jmap," which is a command-line tool that prints memory-related statistics, but the command returns either an "Access Den...
Linux users can use the following steps to determine which of their Java threads is consuming the most CPU. From your computer terminal: 1. First, find the Java process ID. ps -ef |grep java 2. Use the Java process ID (PID) to pull the lightweigh...
Symptoms Use this split rule if you have an arraylist <String>, and you need to fetch the value of pincode in the data collector so that anyone can use that data collector in analytics to retrieve results. java.util.ArrayList<String> customerList = n...
Now, these users will only need to sign in to AppDynamics once. As they navigate from one to another of their authorized AppDynamics products and services, they will not be asked for their password again.
NOTE | This change does not affect current Controller local, SAML, and LDAP users, who can continue to sign in as they always have, without disrupting their access.
Though this feature is currently only available for users added since v21.11, the ability to convert an existing (pre-v21.11) user account to the new SSO-enabled AppDynamics managed user identity is planned for later in 2022. Be on the lookout for an announcement describing this conversion in the future.
AppDynamics IDP users can use the following steps to view and navigate to their AppDynamics products and services:
|
The password field appears once you enter the username and click next. It may either appear on the same screen, or once you are redirected to your “global” sign-in page.
You need to enter your username twice when first signing in due to our use of a global identity provider.
TIPS | Use the “Remember me” functions to further streamline all your future logins.
Alternatively, sign in to your personal profile page first. It will show you everything you have access to and provide direct access links.
We are working on a migration to AppD IDP user capability that will upgrade your existing Controller account to AppD IDP. It is on the roadmap for later this year.
You can expect successful authentications when an AppD IDP account is used for a service account AppD IDP authentication on a Controller. The service account can be authenticated without the SSO flow.
That said, we recommend that customers move to our OAUTH-based API clients for this process , wherever possible, to improve security. See the documentation for this feature here.
AppD IDP stands for “AppDynamics Identity Provider”. Until now, each Controller has served as its own identity provider. From this point forward, we are moving that function to the AppD IDP, a global AppDynamics Identity Provider.
If you have chosen SAML or LDAP as your authentication provider in the Controller tenant authentication provider settings tab, then you are not using the new AppD IDP for user identity management, but instead are using your own provider. If your Controller tenant has “AppDynamics” selected in the Controller tenant authentication provider tab, then users created since v21.11 are using the AppD IDP for user identity management.
If your account was created between now and v21.11, and your email address is your username, then you are an AppDynamics Identity Provider user.
You can confirm this by logging into your personal profile at https://accounts.appdynamics.com/personal-profile. If the Assigned Controller Tenants sections lists the Controllers you use, you are an AppDynamics Identity Provider user.
Legacy local AppDynamics user accounts are those created before v.21.11 that do not use email as their username.
NOTE | As with Controller based SAML and LDAP users, current pre-v21.11 legacy local users can continue to sign in as they always have, without a disruption to their access.
Yes! This is like any other AppDIDP-managed user except that when they sign in, they will be redirected to the customer IDP. Just add the user using their email address to the Controller account.
The user must be added from the Controller users page, using their email address. If a user’s email exists in the AppD IDP, that account will be used for SSO features.
NOTE | Users cannot be given access to a Controller tenant from the Accounts Management Portal at this time.
You may find the following AppDynamics Documentation resources useful:
Also related to this topic are the following Knowledge Base articles:
Bill.Howard
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form