Filtering Alarms. Dell Vizioncore

Add to My manuals
235 Pages


Filtering Alarms. Dell Vizioncore | Manualzz

Working with Services and Alarms

Filtering Alarms


To edit a service name:

1 On the Service Builder dashboard, click Edit for the service name you want to change.

The Edit Service Descriptions dialog box appears.

2 Change the name and click Update . The service name is changed but the service state is not altered.

Editing a Service Description

You can change the service description that is displayed when you hover over a service that is listed on a dashboard.

To edit a service description:

1 Click Edit for the service you want to edit.


The Edit Service Descriptions dialog box appears.

Modify the descriptions and then click Update .

Filtering Alarms

Alarm filters can be defined for any service or application tier instance in the Service

Builder. You can use alarm filters to specify alarms that are relevant to a given service as a way to keep an irrelevant alarm from falsely causing a service outage, rather than have all alarms impact the state of a service.

For example, alarm filtering can be used to ignore a certain state for a component with a high CPU usage. vFoglight is monitoring an application that runs on a Weblogic server and you create a service called "Retail" that includes the server and the host. The

"Retail" service is shown as being unavailable when the host has a CPU usage greater than 90%. However, generally this is not considered a true service outage for this

116 vFoglight

User Guide service. If you look at the host alarms none of the alarms apply to the Retail service. As a result, you can use an alarm filter to filter out all host rules.

In another example, you can use an alarm filter to ignore the state of a service that appears as unavailable when the file system component for the D: drive fills up. vFoglight is monitoring an application that uses a host for the Siebel database and you want to filter out the Oracle database. The database is configured so that it uses only the

C: drive, not the D: drive. A service was created to monitor the application that includes the Oracle agent and the host instance for the Oracle host. However, the service shows as unavailable if the D: drive fills up. Since the D: drive does not contribute to the availability of the application, you should add an alarm filter to exclude the monitoring of the D: drive. You can restrict the filter by choosing the FileSystem alarm, then specifying a Groovy script to refine the filter to apply only to the D: drive.

Adding an Alarm Filter

By specifying an alarm filter, you can decide what alarms impact the availability of a service.

To add an alarm filter:

1 From the navigation panel, under Dashboards , click Services > Service Builder .

2 Drill-down to the component and click the Alarm Filters button.

The Alarm Filters dialog shows alarms inherited from parents of the current service.


Note Alarm filters can be defined for two nested services. Alarm filters work the same way regardless they are nested or not. Even though a set of alarms is not filtered out by the alarms’ immediate parents, the set of alarms are eventually filtered out by an alarm filter defined for one of the alarms’ parents further up the hierarchy of nested services.

You can select an existing filter from the list or click

The Add Alarm Filter dialog appears.

to add a new filter.

Working with Services and Alarms

Filtering Alarms


4 Select one or more filtering options:

• By Rule —select the By Rule check box and choose a rule to monitor one or more of the nested children added to the service. You can define more than one alarm filter for the same rule.

• Alarms —select the state of alarms to include or exclude:


- Include : all alarms are excluded except those specified in the include filters.

- Exclude : all alarms are included except those specified in the exclude filters.

- If both Include and Exclude filters are defined: include alarms that are specified in the Include filters as long as they are not excluded by the Exclude filters.

• Groovy Script —an optional script used to refine the filtering. An alarm is the only required input, meaning you can filter on anything that is referenced by the alarm. An example of a groovy script is:

@alarm.get('topologyObject').getType().getName() ==


Click Save .

The filter is saved on the Alarm Filters list.


Related manuals

Download PDF


Table of contents