AppD Archive

Snapshot - missing 3rd Tier

CommunityUser
Splunk Employee
Splunk Employee

Hi

Although flow maps show the complete transaction travelling through all 3 tiers, in a (manual) snapshot I can only see the first 2 tiers. If the snapshot is started from tier 2 I can see tier 2 and 3. 

My understading is, that all tiers should be included in a snapshot (from a diagnostic session) - even in AD version 3.7, so I wonder, what I could do about that:

- how to troubleshoot?

- is there a technical limiation? All tiers run JBoss, EJB, communication RMI

- could there be a misconfiguration (entry/exit points)?

Thanks for your help!

Regards

Markus

0 Karma

Arun_Dasetty
Super Champion

Hi Markus,

 

There is know desing change for correlation but this is for RMI exit calls , Can you please provide following details to get clarity over the issue:

- screenshot from Controller UI depicting the issue

- archive version of agent logs from both upstream (tier that makes calls to missing tier) and downstream tier

- type of exit from upstream tier to missing tier

- API (class and method details) involved in both the tiers/jvms that process exit call between two tiers

 

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun 

Thanks for your reply. I have to check with the customer, if I can upload log files. Can I send  the files to your personal mail account? Attached is a flow map, I just erased the node names.

I checked my test 3 tier application and even in that one, running AD 4.0.x I sometimes see missing tier snapshots. Although not nesseseraly from tier 3. Can a downstream snapshot not be generated due to snapshot limit per time interval or short execution time? In snapshot settings there is a minial method response time threshold of 10ms. 

Thanks + regards

Markus

0 Karma

Arun_Dasetty
Super Champion

Hi Markus,

You could be right, There are cases where the snapshot limit could affect as well, please fee free to send logs to akumar@appdynamics.com 

Snapshot minimal response time 10 ms is not related to snapshot collection failure, but it could be the case that agent node associated to Tier3 might have failed to snapshot for this request due to different reasons like connectivity issues, or an agent error in generating snapshot as such.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...