EUEM - How the First Public IP field is populated in a page or session record?

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Real End User Experience Monitoring


    COMPONENT:

    TrueSight Collector


    APPLIES TO:

    BMC Real End User Experience Monitoring



    DETAILS:

     

    The First Public IP system primitive custom field in BMC Real End User Experience Monitoring (EUEM) is populated in the Real User Collector.  It is defined by default as:

    Left most non "reserved" IP Address value of the X-Forwarded-For HTTP request header 
    OR
    Client IP if the above is not available.

    The X-Forwarded-For header is an optional HTTP request header. If it is present it will have a list of space separated IP address values. EUEM will parse this header and find the first IP address that is not in the LAN "reserved" list: 10.x.x.x, 192.168.x.x, 172.16.x.x..  The resulting value will be an IP address reachable on the Internet.

    Every time a HTTP transaction is processed by EUEM it will become an object in the Real User Analyzer database. The First Public IP will be evaluated for each object.

    When looking at a page record or a session record in the Analyzer,  the Client IP for the record will be from the first object of the page or session but the First Public IP for the record will be from the last object of the page or session.

    This can cause confusion for users who wonder why the Client IP and the First Public IP values differ.

     


    Article Number:

    000133653


    Article Type:

    Product/Service Description



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles