Application Component, Application Component by City, Application Component by Country, Application Component by ISP, Application Component by Region, Application Component by Server, Application Component by Subnet, City, Country, Enterprise, HTTP Protocol, ISP, Region, Site, Subnet, User Agent, Instrumented Application Component, Instrumented Application Component by City, Instrumented Application Component by Country, Instrumented Application Component by Region, Instrumented Application Component by ISP
This metric shows the number of user sessions that were active during a specific time interval. A session is uniquely identified by its session ID and configured in the web console on the Configure > Monitoring > User Sessions page.
A user session is considered active whenever the user opens a new TCP connection within the session. An existing user session is considered active if the user sends or receives any messages over one of its existing TCP connections during the time interval.
This metric does not reflect inactive sessions that generate no traffic during a five-minute time interval. For example, assume a session is active at 8:02 and then again at 8:12. Only the 8:00-8:05 and 8:10-8:15 intervals have that session included in the calculation for this metric. The 8:05-8:10 interval does not include the session since it was inactive during that time.
For real-time, hourly, and daily time intervals, the metric is incremented the first time a session ID appears in a time interval. To ensure that the count is only incremented once for the interval, a table of all session IDs discovered in the monitored traffic during the interval is maintained.
This field contains the identifier assigned by the web server to uniquely identify an individual user session. Typically, web servers store state information about the user's session (such as items in their shopping cart) and use this session key in a database lookup to find the users state.
Sessions keys are different from the . They are typically assigned the first time a user accesses a web site and maintained across the entire user session. A login name is only required when the user tries to perform a privileged operation on the web site (such as checking out items in shopping cart). The session key is completely hidden from the user and only used by the web site infrastructure.
See “Identifying user sessions” in the Foglight Experience Monitor Installation and Administration Guide for information on how to configure this feature.
This metric reflects the amount of time users spend on a site. A user's session with the site starts with the first packet the user sends to a server that contains the site and ends with the last packet the received from the user. When the user has not been active for five minutes or longer, the session has ended.
For each user that accesses a monitored site, the site session start time is recorded for their first page view on that site. With each additional page view on the same site, the site session stop time is updated with the current time. When a user clicks to a different site or becomes inactive, then the site session time is updated as follows:
For each SOAP Operation, this metric shows the amount of time spent on the client side of the network where a consumer of SOAP services is located. This includes the network delay in sending the data block, the time the client spends processing the data block, and the network delay needed to transmit the acknowledgement. While processing a single command, there may be several data blocks that are sent, processed at the client, and then acknowledged.
The response generated for a request is transmitted back to the client in one or more blocks. Each block of data sent to the client must be acknowledged by the client before the server sends the next block. Often, the client must do some processing of the data it received before it can send an acknowledgement back to the server. Once all of the blocks sent by the server have been acknowledged by the client, the command is complete.