topic Re: Appdynamics only showing Memory based metrics. Java API using spring 5 + Reactor + Spring boot 2 in Splunk AppDynamics

Appdynamics only showing Memory based metrics. Java API using spring 5 + Reactor + Spring boot 2

CommunityUser — Sun, 11 Mar 2018 22:57:40 GMT

Using the tech stack above, appdynamics only shows Memory metrics and JMX. I assume the above libraries are too new for appdynamics support. Am I able to manually add api endpoints using class names and methods?

Re: Appdynamics only showing Memory based metrics. Java API using spring 5 + Reactor + Spring boot 2

Peter_Holditch — Tue, 13 Mar 2018 09:24:08 GMT

Reece,

You can absolutely add custom "POJO" entry points and custom exit points to detect activity within any framework that is not supported out of the box.

Exactly what entries and exits is your application using?

Warm regards,
Peter

Re: Appdynamics only showing Memory based metrics. Java API using spring 5 + Reactor + Spring boot 2

CommunityUser — Wed, 14 Mar 2018 23:30:15 GMT

Hi Peter,

Ive added our own packages to the POJO entry points and it detects that theyre being hit, however response times dont work, I believe due to the nature of "reactive" frameworks ie a business transaction doesnt take place on the same thread. From what I can gather theyre created and deleted indirectly of the preceeding operation.

Is there anyway I can get response times at all?

Thanks,

Reece

Re: Appdynamics only showing Memory based metrics. Java API using spring 5 + Reactor + Spring boot 2

Peter_Holditch — Thu, 15 Mar 2018 05:00:13 GMT

Reece,

For now, you can configure a method to serve as an asynchronous transaction demarcator (presumably, the method which sends the reply) and that will measure the response time for you.

Is your code running in the context of a Spring Boot 2 servlet? If so, once we have added out of the box configuration for spring boot 2 then the ttransactions should be detected automatically with the correct response times.

Warm regards,
Peter