In addition to User Session category metrics, a triggered alarm that is based on metrics in the category Application Component, Subnet, Page, or Hit can also cause a user session to be recorded. These metrics allow you to select a Data Point statistic when defining the alarm (the “statistics” drop-down list is displayed only for this type of metrics). See for more information about setting basic alarm behavior.
With User Session category metrics, the statistic to which the alarm threshold is compared can be set to Maximum, Minimum, Mean, or Standard Deviation. These statistics represent metrics collected during the entire user’s session. When a Data Point statistic is selected, it allows a single data point during an individual user session to trigger an alarm if a threshold is violated.
The ability to fire an alarm when a user session violates a given threshold on a specific web page helps you pinpoint specific problem pages through the User Sessions Log. By using the Originating Alarms box in the Sessions Log, as discussed on page 33, you can filter through the entries to find the sessions that encountered poor performance with the given page.
The App Data Point alarm triggers if the Page End-to-End Time in the Application Component category is greater than one second when monitoring Collect Receivables data. Any alarms trigger during traffic monitoring can be viewed in the Log page.
By clicking the App Data Point link, the All Metrics View > User Session opens and displays alarm information and metric information for that user. From the User Session Pages section, metrics for the user shows that the End-to-End Time for a page was over one second, based on the alarm threshold which was set for any Page End-to-End Time metrics over one second.
Alternatively, you can navigate to the User Session Log, and from the Originating Alarms drop-down box, select the App Data Point alarm. User Session that have triggered an alarm display in the Identifier column. Select an IP address of the User Session to view the alarm information.
For more information, see “Recording user sessions” in the Foglight Experience Monitor Installation and Administration Guide.
In the User Sessions Log, user information can show login names or originating IP addresses, and subnet or originating city. The usability of the Sessions Log is under the control of administrators, who need to set up user session identifiers.
For more information, see “Identifying user sessions” in the Foglight Experience Monitor Installation and Administration Guide.
When you click a recorded user session’s identifier (for example, the IP address, or login name associated with the user session) you are shown an All Metrics View. This page includes all metrics for the entire user session.