Looks like my calculations were warped by this bug: https://bugs.openjdk.org/browse/JDK-8307488?force_isolation=true When I throw out of first sample of each thread, the results make a lot more sense. ... View more

@JohnGreggFrom what I've read, Java agents should be dividing by processor count: CPU millis / time / processor_count But if you're not seeing that in your K8s results, maybe the cluster agent works differently than regular Java agents? For the cluster agent metrics, I know it treats 1 CPU = 100%, so multi-core usage gives you >100%. Might be worth checking if you're looking at app agent metrics vs cluster agent metrics - they could calculate differently. If this helps, Please Upvote. ... View more

Ok, I'm pretty sure my theory is right. Look at this stack trace: at org.apache.http.impl.BHttpConnectionBase.close(BHttpConnectionBase.java:317) at org.apache.http.impl.conn.LoggingManagedHttpClientConnection.close(LoggingManagedHttpClientConnection.java:81) at org.apache.http.impl.execchain.ConnectionHolder.releaseConnection(ConnectionHolder.java:103) at org.apache.http.impl.execchain.ConnectionHolder.close(ConnectionHolder.java:156) at org.apache.http.impl.execchain.HttpResponseProxy.close(HttpResponseProxy.java:62) at com.signalfx.signalflow.client.ServerSentEventsTransport$TransportChannel.close(ServerSentEventsTransport.java:385) at com.signalfx.signalflow.client.Computation.close(Computation.java:168) If you use a debugger to print the identity hashcode of the inBuffer variable that is being cleared on that line, you'll see that it is the same object that is later returning -1 bytes read at org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedInputStream.java:250), which causes the MalformedChunkCodingException. This is a bug in your SDK. Changing TransportChannel's close() method to be more like this seems to fix the problem: public void close() { super.close(); this.streamParser.close(); try { this.response.close(); } catch (IOException ex) { log.error("failed to close response", ex); } try { this.connection.close(); } catch (IOException ex) { log.error("failed to close connection", ex); } } In that case, the wire logger output shows the trailing chunk: 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "event: control-message[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "data: {[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "data: "event" : "END_OF_CHANNEL",[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "data: "timestampMs" : 1751387752387[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "data: }[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "[\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "[\r][\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "0[\r][\n]" 2025-07-01 11:35:52.923 CDT | FINE | org.apache.http.wire | http-outgoing-2 << "[\r][\n]" thanks ... View more

Thanks.  I'm thinking it might have been a time sync issue.  If I set the start time slightly in the past, like even 1 second, it works. What I've settled on is setting the start time on the minute (no seconds) with the same value for the end time.  That seems to return the single record that I want. thanks ... View more

OK, cool, thanks for the more info. That’s giving me more confidence that what you were originally seeing is a reflection of data roll-ups. That being said, I think the “more recent” timestamp is “correct” because the value at that timestamp represents a roll-up of the past X amount of time. For your use-case and reliably grabbing the “past minute”, I wonder if it would be a good idea to make that minute well-defined by specifying start_time and end_time instead of just “-1m” so you avoid edge cases where a datapoint might arrive late for some reason out of your control (network latency, java agent metric export, etc). So maybe the minute you query is something like from (now -2 mins) to (now -1 min). Once the data arrives at the Observability Cloud ingest endpoint, I don’t think you have to worry about any delay with ingest. The data will be recorded as it streams in even when something like a chart visualization appears to have a delay in drawing. I’d be more concerned about any potential latency from the point in time that the metric is recorded (e.g. garbage collection in the java agent) to the time it takes for the agent to export that datapoint and the time it takes for that datapoint to traverse the network to the ingest endpoint. The timestamp on the datapoint will reflect the time it was recorded even if takes extra time for that datapoint to arrive at ingest (e.g., datapoint is recorded by java agent at 16:04:01 but arrives at ingest endpoint at 16:04:45 due to some temporary network condition) ... View more

Tried need-props=true.  All it added was Servlet URI, EUM Request GUID, and ProcessID.   thanks   ... View more

No, that's not it.  Thanks ... View more

Hi @John.Gregg, Thanks for asking your question on the Community. It appears the community has not jumped in with a reply yet. Did you happen to find any new information or a solution you can share here? If not and you are still looking for help, you can contact AppDynamics Support: How to contact AppDynamics Support and manage existing cases with Cisco Support Case Manager (SCM)  ... View more

Hi @John.Gregg, I was not able to find any existing content on this. We're you able to figure anything out you could share? If not, you can contact Support. How do I submit a Support ticket? An FAQ  ... View more

Hi @John.Gregg, I have not heard back from the Docs team yet. You may want to submit this as a bug in a ticket. I sent you a PM about how your account shows up in community too.  How do I submit a Support ticket? An FAQ  ... View more

Hi @John.Gregg, Thanks a lot for following up!  ... View more

Hi @John.Gregg, Thank you for your question on the community! First of all, the granularity you can get via REST API is different from the Controller UI. You can get recent data with only the following granularity via REST API: - 1-minute granularity for the last 1 day. - 10-minute granularity for the last 2 day. On the other hand, a resolution of metric data on the controller UI depends on a time range you select. Also please take note that all data at 1-minute resolution is deleted after 8 days as described in the link below: https://docs.appdynamics.com/appd/21.x/latest/en/appdynamics-essentials/metrics-and-graphs/metric-data-resolution-over-time#id-.MetricDataResolutionoverTimev21.1-MetricsDataRetentionandDeletion Best regards, Hirokazu ... View more

Hi @John.Gregg, I did some searching and found this. It seems API can be used to initiate a thread dump, but not download. https://docs.appdynamics.com/21.5/en/extend-appdynamics/appdynamics-apis/alert-and-respond-api/actions-api#ActionsAPI-Example Example Request Response This example creates an action of the type Thread Dump. See Download Examples. { "actionType": "THREAD_DUMP", "name": "Thread Dump Action", "numberOfThreadDumps": 2, "intervalInMs": 500, "approvalBeforeExecution": { "requireApproval": true, "approverEmail": "email@website.com" } } ... View more

Hi @John.Gregg , Thank you for posting to the community. "Compatible with 4.4.1.0" means the agent is compatible with any Controller having version >= 4.4.1.0, so it shouldn't be a problem if the controller's version is greater than 4.4.1.0. Could you please check the followings?   ・Could you please check the Prerequisites for Object Instance Tracking again, especially the OS version? From the Java supported environments, oracle jvm supports Solaris Sparc 64, Windows, Linux, so if you are using MacOS, Object Instance Tracking may not be available. https://docs.appdynamics.com/21.6/en/application-monitoring/tiers-and-nodes/monitor-jvms/object-instance-tracking-for-java#ObjectInstanceTrackingforJava-PrerequisitesforObjectInstanceTracking   ・Where did you get the warning about missing tools.jar or needing to use an Oracle JVM? If it is a popup that appears after selecting ON on the Object Instance Tracking subtab, it always appears even if Object Instance Tracking is available. Then, after selecting OK and get "Error Saving Items" message, there can be a permission issue, so please confirm that your role has "Configure Agent Properties" Edit Permission on the application.   ・After enabling the Object Instance Tracking from the controller, could you please look at the agent log and see logs related to ObjectMonitoringService? If there is a log like "Object Instance Monitoring cannot be enabled on this platform," the platform may not be supported. Best Regards, Hiroki ... View more

Hi @Nawaz Ali.Mohammad  Would you please confirm if there is still no public API to fetch the JVM details ? Also, is there a public API to get the application language, e.g. Java, NodeJS, PHP ? If not, is it possible to use custom attributes to get such details? Or can we access/execute a query through an API call? ... View more

Hi There Unfortunately, unlike servlets, there is no auto option for e.g configuring AppDynamics to split it based on the number of URI segments etc. The way we do it(Unless you already have the full list of WebService endpoints), is to use e.g Live Preview for Java Nodes to check the http requests, that will give you the full endpoints. And then you configure Web Service rules for each. Or if you have analytics, you can get the full url of the actual request. For large environments, where there are a great number of these, we automated the import of the Web Service rules via the API.(As it is time consuming doing them manually for a large number of transactions Ciao ... View more

Casting is the process of type conversion, which is in Java very common because its a statically typed language. Type Casting only works when the casted object follows an is a relationship to the type you are trying to cast to. ClassCastException is a runtime exception raised in Java when you try to improperly cast a class from one type to another. It's thrown to indicate that the code has attempted to cast an object to a related class, but of which it is not an instance. It is good practice to guard any explicit casts with an instanceof check first: if (myApple instanceof Fruit) { Fruit myFruit = (Fruit)myApple; } In general, that's what a cast means: it tells the compiler that even though this assignment might fail, you're pretty certain that it won't. In exchange for allowing the code to compile, you assume the risk of a run-time exception. Here are some basic rules to keep in mind when casting variables: Casting an object from a sub class to a super class doesn't require an explicit cast. Casting an object from a super class to a sub class requires an explicit cast. The compiler will not allow casts to unrelated types. Even when the code compiles without issue, an exception may be thrown at run time if the object being cast is not actually an instance of that class . This will result in the run time exception ClassCastException. ... View more

The active processor count doesn't itself limit the number of CPUs the JVM can use in a general way.  Would you expect this option to only be used in combination with other features? Here is an example of CPU usage during a load test.  Active processor count was 4 but there were 8 CPUs on the machine and you can clearly see all 8 CPUs being used equally. 8 CPUs used equally As it is, the calculated process CPU usage is incorrect for cases where the total CPU count is greater than the specified active processor count. thanks ... View more

When configuring a JMX metric, there is an option to use the delta between this and the last value; is this a fix for your user case?     ... View more

Hi @Ravi.Rajangam,  I updated the link above. If this ever happens again, just look at the last bit of the URL, it shows you the title of the doc and you can search for the title in docs. https://docs.appdynamics.com/appd/24.x/24.4/en/application-monitoring/administer-app-server-agents/request-agent-log-files ... View more