Hi all
for a specific JVM, I would like to instrument it with the JavaAgent and get memory and JMX metric. But I know that I will never get/want BusinessTranscation data from this JVM, and thus I would prefer to turn off the call stack sampling and...
Hi
we're using AppD 4.3.5.7 and I'm trying to configure Service Endpoints correctly. Until now, I only optimized detection rules for BTs, which in our case are exclusively WebService from the Java agent.
Lately I learned that to get the FULL metrics ...
Hi
we're currently using AppD 4.3.5.7 and I just read the new release notes of 4.4. The Java Agent 4.4 would have 2 very important enhancements for my use-case
support for the Apache Async HTTP Clientenhanced support for Kafka (and Akka)
My question:...
Sorry for the late response, I was away for a few days.
Turns out that all my problems (supposedly missing metrics) was actually just impatience on my side.
For me in my installation it became apparent that after changing discovery rules, I really ...
Not exactly. The full chain could be something like
A1 -> S3 in A3 -> S7 in A7
So the call chain starts in A1. Service S3 (hosted on a tier within A3) is called. Here the BT starts, and S3 is nicely shown on the BT dashboard (and service e...
Hi Gurmit
Thanks for you insights! I perfectly agree with you as long as your are looking at it from the viewpoint of 1 single AppDynamics application.
I was not clear enough on that, but in my case we have ~12 different AppD applications, each w...
Hm, I guess I don't even need to try, the notes say
AppDynamics agents are not backwards compatible with the AppDynamics Controller. The Controller version must be equal to or greater than the versions of any agents connecting to it.
No joy...