Splunk AppDynamics

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

CommunityUser
Splunk Employee
Splunk Employee

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?

Labels (1)
0 Karma

Peter_Holditch
Builder

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

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

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

0 Karma

Peter_Holditch
Builder

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

0 Karma
Get Updates on the Splunk Community!

Enhance Your Splunk App Development: New Tools & Support

UCC FrameworkAdd-on Builder has been around for quite some time. It helps build Splunk apps faster, but it ...

Prove Your Splunk Prowess at .conf25—No Prereqs Required!

Your Next Big Security Credential: No Prerequisites Needed We know you’ve got the skills, and now, earning the ...

Splunk Observability Cloud's AI Assistant in Action Series: Observability as Code

This is the sixth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...