topic Re: Remote Service actually another App on the same controller in Splunk AppDynamics

Remote Service actually another App on the same controller

Jeffrey_Escamil — Wed, 21 Aug 2024 16:05:25 GMT

So I've run into a weird issue where most all my apps show up as a web, and you can see where calls from one app, are made to another app. All except one. In this one, connections to other apps just show up under the "Remote Services" page with the FQDN listed. As such, the dashboard view doesn't correctly link it. Is there a way that I can say that a specific remote service is actually connected to another app? All the documentation I've found tells you how to rename it to a tier within the same app.

Re: Remote Service actually another App on the same controller

iamryan — Fri, 23 Aug 2024 14:38:00 GMT

Hi @Jeffrey.Escamilla,

It looks like the community has not yet jumped in to reply. Have you happened to find a solution or more information you can share?

If you still need help with this question, you can reach out to your CSM or contact AppDynamics Support: AppDynamics is migrating our Support case handling system to Cisco Support Case Manager (SCM). Read on to learn how to manage your cases.
If you get an answer, it would be helpful if you could come back and share it here.

Re: Remote Service actually another App on the same controller

Jeffrey_Escamil — Wed, 28 Aug 2024 14:01:51 GMT

Currently have an active case open. Will gladly share the results when I get them!

Re: Remote Service actually another App on the same controller

Morelz — Mon, 02 Sep 2024 10:53:22 GMT

As you mentioned, you can only manually link it if it's within the same app.

That said, you should fix the actual correlation issue, which will correctly link it to the other application. This might just be due to the correlation not being picked up on the downstream application. Should be a quick fix

Re: Remote Service actually another App on the same controller

iamryan — Mon, 09 Sep 2024 20:49:29 GMT

Hi @Jeffrey.Escamilla,

I know we had some issues with community access last week. You can come back to comment and create content again.

With that in mind, if Mario's answer helped you out, please click the 'Accept as Solution' button on the reply that helped. If you need more help, reply back to keep the conversation going.