Discussion Feed

Peter.Holditch

Is the server hosted in a container? If so, you may have trouble with entropy. Try putting -D appdynamics.low.entropy=true on the JVM command line. If that does not help, can you post a thread dump taken from the JVM during startup? Warm regards, Peter

Peter.Holditch

AppDynamics' offers initial Oracle Java 14 Beta build certification test results with Java Agent v20.3.0 Table of Contents Overview: Java 14 and AppDynamics Support Java 14 Beta build test results Overview Since September 2017, the Java roadmap includes LTS releases every 3 years in September with incremental releases in March and September, each with a 6 months support window. For AppDynamics, supporting a new Java version includes 2 aspects: Agent certification on the new release Product enhancements to leverage platform new capabilities. . AppDynamics Java 14 Support We intend to support Oracle Java 14 as soon as possible. The Java 14 beta drop passed all the validation tests with our publicly available Java Agent v20.3.0. Depending on further testing, we might announce formal Java 14 support with this 20.3.0 release or the 20.4.0 one currently scheduled for the 3rd week of April 2020. Java 14 Beta build test results Below is a representative sample of the initial validation tests conducted with the Java 14 Beta builds and their individual results. In summary, all these initial tests have passed successfully with Java 14 Beta builds. Test Result Application startup and Agent Registration Pass Simple Servlet Application deployed in Tomcat 9 Pass, verified for its startup, monitoring and metrics flow POJO application on AppDynamics Controller v20.3.0 Pass, verified the exchange of agent configurations with: Controller Flow map diagrams Metrics Snapshots capture Agent Logs Pass, no errors or exceptions occurred

Peter.Holditch

Rohde, Can I ask what kind of server-side projects you are developing using kotlin, and which frameworks you are using? Warm regards, Peter

Peter.Holditch · Re: analytics-agent-4.5.13.951 Version compatibili...

Mudassir, I will file a ticket to improve the documentation in this regard; the analytics agent requires java 1.8 or higher to run, as is mentioned here. (if a java application agent is reporting the data, the application JVM that sends the data to the analytics agent for processing can be any version supported by the java agent) Warm regards, Peter

Peter.Holditch

Kjell-Einar, It's at least implied in the documentation here Warm regards, Peter

Peter.Holditch

The exclusion will be actioned on the agent side, so the agent will ignore the excluded activity.

Peter.Holditch

Catherine, I'm delighted that got you going. If you have any suggestions as to how we could make this easier to find in the documentation, please let me know. From the inside, it's easy to take too much for granted. What search terms did you try to use to find this? Where would you expect to see it? Warm, regards, Peter

Peter.Holditch · ‎03-03-2020

John, You are correct that this is the method used to calculate this metric. The net result is that it measures the CPU consumption as a percentage of the resources that the JVM user declared were allocated to the JVM, a measure that is useful to some customers, so just changing the way it is calculated is problematic. It is possible to track the process CPU consumption vs the resources of the entire machine using the SIM agent Does this latter method address your needs? Warm regards, Peter

Peter.Holditch · ‎03-03-2020

Catherine, You should create an exit call object and obtain the outgoing correlation header from that, as shown in the code sample in the documentation here: https://docs.appdynamics.com/display/PRO45/.Manual+Tracer+Instrumentation+v4.5.x#id-.ManualTracerInstrumentationv4.5.x-exit I pasted the relevant section below: //Define the createExitCall method to obtain an exitCall object. ExitCall exitCall = transaction.createExitCall(callType, identifyingProperties); outgoingHeader = exitCall.getCorrelationHeader(); exitCall.start(); try { // Tracer.APPDYNAMICS_TRANSACTION_CORRELATION_HEADER_KEY is the name of the header that should be set if (outgoingHeader != null) { conn.setRequestProperty(Tracer.APPDYNAMICS_TRANSACTION_CORRELATION_HEADER_KEY, outgoingHeader); // set the correlation header on an HttpURLConnection } // Make the exit call here } finally { exitCall.stop(); } }

Peter.Holditch · ‎02-27-2020

Catherine, It appears that the value of the correlation header you are trying to consume on input is " com.appdynamics.serverless.tracers.aws.correlation.CorrelationHeader" That is definitely not a valid header, where did you obtain it from? To give you an idea of what you should be expecting to see, an example of a valid header is: appId=4113*ctrlguid=1539290818*acctguid=e2c8a068-be66-46a4-a0d3-aeff5f18ecc9*btid=532007*guid=efbe5515-1e93-496c-9f53-47c1640069e73*ts=34869499416608*cidfrom=7500*unresolvedexitid=139411*exitguid=40*cidto={[UNRESOLVED][139411]}*etypeorder=HTTP You should get a string of that form returned to you when you call getCorrelationHeader() on the ExitCall object you created in the upstream lambda. Warm regards, Peter

Date Registered	‎01-23-2013 01:54 AM
Date Last Visited	a week ago
Total Messages Posted	312
Total Kudos Received	85

Discussion Feed

Re: After Integrating with Appd, Ping Access is ta...

Java 14 Beta builds tested with AppDynamics Java A...

Re: Support for KOTLIN

Re: analytics-agent-4.5.13.951 Version compatibili...

Re: Configuration feedback from Controller to JVM ...

Re: Configuration feedback from Controller to JVM ...

Re: Java serverless not correlating due to due to ...

Re: Process CPU % is incorrect?

Re: Java serverless not correlating due to due to ...

Re: Java serverless not correlating due to due to ...