Concatenated AXA Sessions
Article ID: 186714
Updated On:
Products
CA Application Experience Analytics SaaS (AXA)
Issue/Introduction
This is a session from a device I was doing application testing.
The test script called for logging out of the application, then logging back in to finish the testing.
There are numerous steps in the second part of the test; I don't see an AXA session for the second portion.
What I see here, given in the screenshot, is the session end when I logged off the application, and then what appears to be the second session appended to this one. In addition to not being its own session, it didn't capture any of the activity that I did in the application.
A large part of the activity in the application was not captured/reported. This includes the 'punchout' event, which is information often sought in the production environment.
We do still have the one line of code in the application that has an explicit session end; that's the only part where the application is doing any management of the AXA session.
There are numerous steps in the second part of the test; I don't see an AXA session for the second portion.
What I see here, given in the screenshot, is the session end when I logged off the application, and then what appears to be the second session appended to this one. In addition to not being its own session, it didn't capture any of the activity that I did in the application.
A large part of the activity in the application was not captured/reported. This includes the 'punchout' event, which is information often sought in the production environment.
We do still have the one line of code in the application that has an explicit session end; that's the only part where the application is doing any management of the AXA session.
Environment
Release : SAAS
Component : CA APP EXPERIENCE ANALYTICS SAAS
Resolution
Custom removed session management from the application code.
Feedback
Yes
No
Powered by
