DX Application Performance Management

  • 1.  How to configurate Interim Session Identification

    Posted Mar 22, 2018 10:17 AM

    Hi,

     

    What values I can defined on Interim Session Identiofication?.

     

    We using cookies to both Session and User identification ( TLTSID and TLTUID respectively)

     

    but, we have this [WARN] menages:

    3/22/18 11:09:59.896 AM CLST [WARN] [DefectLoginProcessingPool.Thread4] [Manager.com.timestock.tess.services.processors.LoginNameProcessor] Session for app def 700000000000000003, session id 'D9BC59BFD334C45CBB81F6341ABFA251', login name '119A0414326A4C97F690B2628116FA58' and interim session id '' already exists

     

    thanks



  • 2.  Re: How to configurate Interim Session Identification

    Posted Mar 22, 2018 11:20 AM

    previous INFO messages to he WARN messsage

     

    3/22/18 10:53:31.580 AM CLST [INFO] [DefectLoginProcessingPool.Thread2] [Manager.com.timestock.tess.util.DbUtils] Session with id 'D9BC59BFD334C45CBB81F6341ABFA251' already exists for login '119A0414326A4C97F690B2628116FA58'



  • 3.  Re: How to configurate Interim Session Identification

    Posted Mar 22, 2018 11:38 AM

    Hello,

    I understand that my problem is not the definition of Interim, but that the session ID we use is not unique for more than one login.

    Our traffic goes through several proxy's, each one adds a cookie to identify a session.

    What tips should I consider to put together a unique session ID?



  • 4.  Re: How to configurate Interim Session Identification

    Broadcom Employee
    Posted Mar 23, 2018 11:22 AM

    Some information on session identifiers here:

    Define Session Identifiers - CA Application Performance Management - 10.5 - CA Technologies Documentation 

     

    In this case, you'll want a value that is unique per session and remains unchanged when passing through proxies. 



  • 5.  Re: How to configurate Interim Session Identification
    Best Answer

    Broadcom Employee
    Posted Mar 23, 2018 02:02 PM

    Side Note:

    In a Multi-Tim environment,  where in more than one Tim reports the same application + login name/id at the same time.

    In another scenario, if Multiple login attempts by the same user if happened within a second.