AppD Archive

Node not detected as a remote service

CommunityUser
Splunk Employee
Splunk Employee

Hi!

how can I configure the node so it'll be detected as a remote service by other nodes?

0 Karma

Arun_Dasetty
Super Champion

Hi Petar,

If we understood your requirement you to monitor calls to particular API(class/method) to be considered as remote backend service, if this is case, Can you define custom exit point as suggested in doc on the api which you want to see a backend and see if that helps:

https://docs.appdynamics.com/display/PRO39/Configure+Custom+Exit+Points

If this is not the case please eloborate the requirement with screenshots and example in UI to assist you better.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi!

first of all, thank you for your reply.

My situation is following: I added two nodes (services with java agents), where one A is calling another B with spring remoting. AppDynamics detected that A is calling "Web service" which is cool. However, it didn't detect that "Web service" is actually node B.

Is there some way to manually configure this?

Thank you

0 Karma

Arun_Dasetty
Super Champion

Hi,

We can do manualy association to a particular for unresolve remote service backend as referred in below screenshot:

image.png

and this helps to link two tiers A and B in flow view but drill down from A to B call graph might not show,

But we would like to see why actually linking is not happening OOTB, can you help us provide the following details:

- screenshot from controller UI depicting the issue from  BT dashboard and another screenshot from app dashboard

- zipped vesion of agent logs from both the nodes from upstream and downstream tier which is A and B tiers in this case , refer steps in screenshots below to collect logs form UI, we will request debug logs if we do not see any suspicious information in info level logs

- API(class/method) details that actually makes exit calls from A tier and API(class/method) details that serves the exit call at downstream tier B for laod made from upstream tier A

image.png

Let us know if that information helps, Keep us posted requested logs to debug further for not getting ootb correlation link between tiers for exit calls made.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...