DX Application Performance Management

Expand all | Collapse all

CA APM CEM show me unspecified user

Jump to Best Answer
  • 1.  CA APM CEM show me unspecified user

    Posted 08-01-2014 01:30 AM

    hi,

    i m using CA APM 9.5 when i m trace the transaction through CEM it show me unspecified user.

    if any body face this problem please suggest what is the issue....



  • 2.  Re: CA APM CEM show me unspecified user

    Posted 08-01-2014 10:47 AM

    Hi,

     

    It is so because you must have defined your Domain application type to be "E-Commerce". If you wld have defined it "Enterprise" it would have shown you the user group \ new user.

     

    Let me know if you need more clarifications.

     

    Regards,
    Vaibhav



  • 3.  Re: CA APM CEM show me unspecified user
    Best Answer

    Posted 08-01-2014 05:34 PM

    It could be your session timeout is low , APM never sees the session identifier. See my tech note for more details (Below)

     

     

     

    Untangling
    the Unspecified User Issue

     

     

     

    Hallett German

     

     

    Consulting
    Architect, Wily Professional Services

     

     

    CA
    Technologies, Inc.

     

     

     

     

    1. Hallett.German@ca.com

     

     

     

     

    Table of Contents

     

     

     

    1. Introduction
    2. What is the Unspecified User Problem?
    3. Guiding Principles
    4. Typical Causes
    5. Etcetera

     

     

     

     

     

     

    Introduction

     

     

     

     

     

    A
    common problem is getting an “unspecified user” in CEM reports. This document reviews
    the unspecified user problem and some common ways to resolve this issue.

     

     

     

     

     

     

     

     

    What is the Unspecified User
    Problem?

     

     

     

     

     

    The unspecified user message typically looks
    like shown below:

     

     
     
     
     
     
     
     
     
     




     

     

     

     

     

     

     

     

    While displaying login name or user group in
    a defect list, an unspecified user(s) appears instead of the actual user name.

     

     

     

     

     

    Have an unspecified user has the following
    disadvantages:

     

     

    1. It
      hinders resolving an issue because the person who logged in is unknown.
    2. Statistics
      for a particular user may be incomplete or misleading due to unspecified users.

     

     

     

     

     

     

     

    An important note:
    There are various times when receiving an unspecified user message may be

     

     

    the expected result.
    An example is an e-commerce website has no login process.

     

     

     

     

     

    Guiding Principles

     

     

    1. When
      working on unspecified user issues, start with the possible easier to find
      causes (such as those associated with authentication type and session
      identifier) and work towards the more complicated ones (such as
      network-related.)
    2. Unless
      it is a case as listed above, most transactions will contain a login name and
      user group. So, unspecified users should be the exception rather than the rule.
    3. There
      should only be one unidentified user per defect.
    4. Only
      Unspecified Users and User Group Request Headers are the only two user groups
      for ecommerce reports.

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    Typical Causes

     

     

    The following are typical causes of
    unspecified user

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     


     

    Cause


     

     

    Reason Why


     

     

    How to Fix


     

     

    Easy/Hard to Detect


     

     

    Session
      Identifier Issues


     

     

    Invalid
      or missing session identifier means CEM cannot differentiate user sessions
      and identify users. This also impacts the binding of the various transaction
      hierarchy elements.


     

     

    -Correct
      text/case in session identifier.


     

    -
      Add or use another session identifier.


     

    -
      If no session cookie is available add a port number (Such as for NTLM
      Authentication and Service Desk without cookie templates)


     

     

    Easy


     

     

    Application
      Type Issues


     

     

    Incorrect
      application type impacts the type of session identifier used. See session
      identifier for reasons why this is happening


     

     

    -Choose
      correct application type (such as Siebel instead of general)


     

     

    Easy


     

     

    Authentication
      Type Issues


     

     

    Authentication
      type impacts the type of session identifier used. See session identifier for
      reasons why this is happening


     

     

    -
      Choose correct authentication type (such as NTLM instead of Basic)


     

     

    Easy


     

     

    Before
      Login


     

     

    If
      a defect happens in the login process, before the user is logged in, there
      will be no user identification


     

     

    Turn
      off defect specifications’ before login or set expectations there will be no
      users for pre-login defects.


     

     

    Easy-Moderate


     

     

    Session
      Timeout Issues


     

     

    The
      user is at a remote location that needs a longer period of time for a session
     


     
    1. Timeout.
     

     


     

    Or
      session timeout is shorter than time needed to login/for a session.


     

     

    Increase
      session timeout. (60 minutes by default).


     

     


     

    You
      can also set the session timeout on the TESS in a file called
      tess-default.properties. It is under
      /etc/wily/cem/tess/tomcat/webapps/wily/WEB-INF/classes/ Here are the relevant
      lines: # when session info is aged out

      session.ageoutAfter_Mins=60


     

     


     

    For the remote
      location issue:


     

    Change
      it to a high value - say 1800 which is equal to 30 hours.


     

    Remember to restart the TESS after you make
      this change.


     

     
    1. Moderate.
     

     

    Redirect
      to External URL


     

     

    Users
      are authenticated are initially seen but an external redirect link is
      clicked.


     

     


     

    Once
      clicked, you can see the transaction but lose the user to session information


     

     

    Increase
      session timeout.


     

     


     

    Use an internal link


     

     


     

    This
      may be in the application/network realm and may not be possible to solve.


     

     

    Hard


     

     

     

     

     

     

     

     

     

     

     

     

    Etcetera

     

     

     

     

     

    Credits
    & Acknowledgements

     

     

    Thanks for Ahana Aman Tur, Joerg Mertin for
    feedback on what to include in this document.

     

     

    Thanks
    to Seth Hammerman, Clayton Johnson, Gautaum Malchandari, and Japeth Ko for
    previously providing notes on this topic on the Wily CEM mailing list.