cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

What is the impact of 100% saturation of session storage queue and Correlation Queue in Appmon?

mallempati_sree
Inactive

hi All,

We are observing High Saturation of Session storage queue and Correlation queue hitting 100% in Appmon resulting in high Skipped PurePaths. But what we have observed is even though in PurePaths the response times is showing <1 second but in the dahsboard its shows much higher like greater than 200 seconds. Is it something related to Correlation queue not able to correlate? Does anyone has any idea why Appmon is showing wrong and highly increased response times when the skipped purepaths occurs

Thanks

/Chetan


4 REPLIES 4

Maybe you have reported Async part of PurePath that takes some time. But transaction in general finished quick for user (he is not waiting for asyncs).

Sebastian


Maybe you have reported Async part of PurePath that takes some time. But transaction in general finished quick for user (he is not waiting for asyncs).

Sebastian


jcurbina
Contributor

Hi Sreedhar,

I recommend that you first solve the problem of high Skipped Purepaths. Check if this is a behavior that appeared only once or has been occurring frequently, through the dashboards of health deployment.
If this is happening frequently, see how to deliver more resources to the appmon server.

See if the number of Purepaths processed per day has increased historically, or at the time when skipped purepaths start to occur.

Juan


BabarQayyum
Leader

Hello @Sreedhar M.

This usually happens due to huge volume of PurePaths to analyze e.g. below chart is for the last 72 hours where you can see a tower of PurePaths and due to this PurePaths were early discarded which considered as skipped PurePaths.
I guess the recommended solution could be to reconsider the instrumentation level or maybe increase of resources can do help in this situation.

Regards,

Babar