Company-internal application is not showing some metrics, including 'Location' and 'ISP'.
We read that in the documentation in the section 'Identifying User Sessions by City or Subnet':
"If you are monitoring an internal application you likely prefer to have the user's subnet displayed in the User Sessions Log rather than the City. When monitoring internal applications, geographical information like City might be inaccurate since that field is determined by the use of a geographic database that maps public IP addresses to cities. If you are monitoring an Internet application, then you would likely prefer to see the city displayed in the User Sessions Log."
Why would the geographical information be inaccurate depending upon whether you are monitoring an internet application or an internal, intranet application. Why would that make a difference?
The geographic database that Foglight Experience Monitor (FxM) uses to determine city/country/region/isp metrics is based on the publicly agreed upon Internet IP addressing scheme. Internal networks (IP addresses that companies use ) don't follow this public scheme. They use whatever arbitrary set of IP addresses they want. The 'ISP' is determined with the use of a database that maps IPs to ISP. If FxM can't look up the IP (due to company-internal addressing scheme), then FxM will not be able to determine the ISP either.
For intranet applications, configure 'Subnets'. Subnets will give the geographic perspective for internal users. Subnets are not configured by default. Subnets are discussed in chapter 4: 'Specifying Monitored Web Traffic' in the 'Installation and Administration Guide'.
More generally, not all metrics show data automatically, by default. It depends on what you have configured FxM to monitor in the web console UI. This is discussed in SOL17049
https://support.quest.com/SUPPORT/index?page=solution&id=SOL17049
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center