Chat now with support
Chat with Support

Foglight Experience Monitor 5.8.1 - User Guide

Installing and configuring Multi-appliance clusters Configuring the appliance Specifying monitored web traffic Transforming monitored URLs Managing applications Foglight components and the appliance Using the console program Troubleshooting the appliance Appendix: Third party software Monitoring the user experience Customizing reports The alarm system Integrating the appliance SOAP-based web services

Editing alarms

You can modify, or view the configuration details for any existing alarm by clicking the alarm name in the list shown on the main Alarm Definitions page. This displays the Alarm Definitions > Edit page.

The alarm editor allows you to modify any settings made when you first created the alarm.

All alarm configuration steps have been outlined in previous sections.

Name and alarm-triggering metric

See Alarm definitions.

Metric types

See Setting alarm options for counter metrics and Setting alarm options for counter metrics.

Resource

See Selecting a resource.

Threshold

See Setting the alarm threshold.

Conditions

See Controlling the alarm.

Actions

See Alarm actions.

After your changes are completed, the appliance starts using the updated alarm definitions immediately. Alarms that are already in the database are unaffected.

Using the alarm log

Alarms are maintained by the appliance for 7 days from the time they are generated. The Log page is accessed by clicking Alarms > Log at the main menu, and provides you with a complete log of alarms that the appliance has generated.

In the Criteria section, you can filter the log by category, severity, and time. Every alarm includes the following information:

See What does an alarm tell me? for information about each of these fields.

Figure 81. Alarm log

By clicking any alarm link in the alarm column the Metric View opens and displays detailed information about that alarm.

The alarm log displays up to 100 alarms on a page. If there are more than 100 alarms listed, use the Next 100 and Previous 100, or page number links to navigate between the pages.

For more details, refer to these topics:

Filtering the alarm log

By using the controls in the Criteria section you can filter the alarm log by category, severity, and time.

By default, the alarm log shows alarms for all categories. By selecting a specific category in the box, you can restrict the list to show only the alarms for that category.

By default, the alarm log shows alarms for all severity levels. However, by selecting a specific severity level in the second box, the Alarm Log can be restricted to show only alarms with that severity level.

The alarm log can show all alarms that have been triggered up to the last 24 hours (the other increments being 2, 4, and 12 hours). By default, the alarm log is set to show all alarms from the last 2 hours.

You can also define a Time Range, during which all alarms that have occurred during that period are listed. To the right of the starting label in the Criteria section are a set of controls that allow you to specify the exact month, day and time you would like the alarm log to use for display. By selecting an earlier date or time, you can display alarms as old as 7 days.

Exploring an alarm

Clicking an alarm on the Alarm Log page takes you to an analysis report or metric view page for the associated metric and resource that generated the alarm. When you click an alarm on a user session, you are taken to an All Metrics View page for the user session.

The alarm threshold is shown on the chart as a red line. This line makes it easy to see where the metric exceeded the threshold causing the alarm. The time range shown on the chart is a 2 hour span from 1 hour before the alarm occurred, until 1 hour after the alarm. The data after the alarm may be less than one hour if the alarm was triggered in the past hour.

In the previous screen shot, the Traceroute section shows the result of a traceroute that was executed when the alarm was triggered. The Status field indicates whether the traceroute was a success or failure. Details of the traceroute including the individual HOP IPs, and the time for each hop are provided in a table below.

Related Documents