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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...