AppD Archive

undo resolve Backends to Tiers

CommunityUser
Splunk Employee
Splunk Employee

I'd like to undo backend to tier resolving., due to an error. The documentation https://docs.appdynamics.com/display/PRO39/Resolve+Backends+to+Tiers suggests the following;

The following Backends are resolved to (point to) this Tier.  If a backend was incorrectly resolved to this Tier, it can be deleted and it will appear on the Application flow map.  A Backend can also be resolved to a different Tier.

I have choosen to delete the backend, the main issue now is that now this backend is not re-appearing on the application flow map as stated in the documentation. I also tried resetting the application agent but this did not help either.

Any other ideas for solving this issue? A last resort might be to delete the application and re-configure it.

0 Karma
1 Solution

Arun_Dasetty
Super Champion

Hi Rajan,

We see you have provided agent logs for weblogic-mhs-tier tier but we do not see any traces of Business trasnactions logged on this tier and we also do not see any JDBC backends traces in agent logs which is expected as no BTs part of the agent node "ac-wls01.acce.alfa.loca" logs provided.

Is the BT is discovered part of "edineparser-tier" if yes, please send the agent node logs from the tier where BT discovered and is expected to make JDBC exit calls, Also provide screenshot of BT dashbaord or BT name details including api expected to make JDBC exit calls to assist you further?

Regards,

Arun

View solution in original post

Tags (2)
0 Karma

Arun_Dasetty
Super Champion

Hi Rajan,

We understood that you have deleted the backend resolved to a tier from tier dashboard -> Actions-> Backends resolving to this tier popup option window as referred in below screenshot, let us know if any disconnect here

If the above said is right, we expect the backend to be discovered for new load on discovered Businss transactions (class/method) under "business transactions" screen  that makes backend calls to deleted/unresolved backends again, Hope that clarifies the product behavior.

If you see different behavior please send the following to assist you further:

- Screenshot from controller UI with app dashboard flow map in view

- zipped version of agent logs 

- Servers ->  Appservers -> Databases/remote services screen in view

image.png

Regards,

Arun

Tags (2)
0 Karma

Jay_Davis
New Member

I am unable to find this menu in 4.1. I have a couple of services that I resolved to a tier. I need to undo. The unresolve from backend tier menu item is not in Actions. 

0 Karma

Arun_Dasetty
Super Champion

Hi,

Check below screenshot We have to check under tier dashboard for which the backend is wrong resolved and to unresolve we need to click "delete" option in popup raised on windows that raised when "connfigure backends to this tier" option menu is clicked,

Are you saying you cannot see the below options?

image.png

image.png

0 Karma

CommunityUser
Splunk Employee
Splunk Employee
 
Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

I did exactly what you posted, the backend MySQL database is not discovered again. Please advice.

Kind regards,

Rajan Arkenbout

Tags (2)
0 Karma

Arun_Dasetty
Super Champion

Hi Rajan,

We do not locate any mysql db reference in previous logs but we see errors related to BCIFixer and mail backend, Can you please confirm the mysql backend name , URL details etc ? Also confirm the following:

- Business transaction that is expected to make db call?

- class/method that is expected to make db call in particualr in call graph for BT snapshot?

- did you checked the mysql backend under Servers -> Databases screen in controller ? we see you are referring to remote services screen where jdbc db will not be listed usually?

Regards,

Arun

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Sorry I have send you the wrong logfile. Look for mhs and mhs_ds

Tags (2)
0 Karma

Arun_Dasetty
Super Champion

Hi Rajan,

We see you have provided agent logs for weblogic-mhs-tier tier but we do not see any traces of Business trasnactions logged on this tier and we also do not see any JDBC backends traces in agent logs which is expected as no BTs part of the agent node "ac-wls01.acce.alfa.loca" logs provided.

Is the BT is discovered part of "edineparser-tier" if yes, please send the agent node logs from the tier where BT discovered and is expected to make JDBC exit calls, Also provide screenshot of BT dashbaord or BT name details including api expected to make JDBC exit calls to assist you further?

Regards,

Arun

Tags (2)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

HI Arun,

I found the issue and this call is resolved.

Thanks for your help.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Rajan,

I got the same problem. Would you mind to share the solution?

Regards,

Julio

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

I resolved it. Just delete the Tier and then it will be discovered again.

Thanks anyway.

0 Karma

Arun_Dasetty
Super Champion

Hi,

We assumme you have deleted the backend from tier dashboard -> Actions-> Backends resolving to this tier popup option window by clicking "delete" option on backend resolved, if this is not the case, and if you have deleted as below, we see that is not a recommended way to delete backend as it will delete tier related data permanently for past data:

from tier dashboard -> Actions-> Delete

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

Say goodbye to manually analyzing phishing and malware threats with Splunk Attack ...

In today’s evolving threat landscape, we understand you’re constantly bombarded with phishing and malware ...

AppDynamics is now part of Splunk Ideas

Hello Splunkers, We have exciting news for you! AppDynamics has been added to the Splunk Ideas Portal. Which ...

Advanced Splunk Data Management Strategies

Join us on Wednesday, May 14, 2025, at 11 AM PDT / 2 PM EDT for an exclusive Tech Talk that delves into ...