立即与支持人员聊天
与支持团队交流

Foglight for Integrations 7.1.0 - User Guide

Using Foglight for Integrations Reference

Configuration View

Purpose

Use the Configuration view to quickly review the MIBs loaded in Foglight. The MIBs table and the Configure Traps table are displayed in this view.

The MIBs table lists the name of the MIB and the date the MIB was last updated. MIBs can be uploaded using the Upload MIB button. When updating, the user is prompted to locate the MIB file. Any errors found while loading MIBs is presented in the user interface.

In the Configure Trap table, a list of subsequent trap definitions associated with the loaded MIBs appears. This table provides a list of traps and their associated MIB name. It also includes the status indicating if the trap is enabled or disabled and the severity of the traps. The Format link allows you to format the alarm information being fed into Foglight.

This view is located in the navigation panel of the Foglight user interface, under Integration > SNMP Trap Administration > Configuration dashboard.

Figure 15. Configuration view

 

Table 11. Configure Trap Properties
Property
Description

Trap Name

The name of the trap that is provided in the MIB file used to load the trap.

MIB Name

The name of the MIB file that contained the trap.

Status

The status of a trap. The status can be either Enabled or Disabled.

Severity

The severity that is given to an alarm that is created when this trap is received.

Format

The configuration options for a Trap.

Trap Variables:

Trap variables are defined in the trap definition and passed in when a trap is received. They are sent as properties on the alarm. They can also be included in the message for the alarm.

Description:

The Description is defined in the trap definition and passed in when a trap is received. It is sent as a property on the alarm. It can also be included in the message for the alarm.

OID:

The OID of the trap as defined in the MIB file.

Message Format:

The message format that is provided on the alarm sent into Foglight based on the trap information. Trap variables can be specified in the message. For example, if the trap variable ifIndex is included in the message, it would be written ${ifIndex}. You can use the variables ${host} ${trapname} and ${technologyMonitor} in the message format. The ${host} is where the trap came from.

Trap Duration:

Forcing an end time on the event sent into Foglight. The end time would be the start time of the trap with the duration added to it. Setting the Trap Duration to zero keeps the trap alarm open until it clears.

 

For more information about how to work with SNMP traps, see Receiving SNMP Traps .

SNMP Trap Groups View

Purpose

The SNMP Trap Group view allows you to group related traps together in order to manipulate alarms associated with the state of an object. Once a trap group is added, you can then add traps to the trap group.

Figure 16. SNMP Trap Groups view

If you choose to edit an SNMP Trap Group, a view of the Traps In Group table and the Ungrouped Traps table is displayed. The Traps In Group table is used to assign variables to make the traps specific to an object. The Ungrouped Traps table lists all traps that were loaded in Foglight. The trap can be included in the trap group by selecting the box next to the trap. When selected, the trap is removed from the Ungrouped Trap list and placed in the Traps in Group table.

This view is located in the navigation panel of the Foglight user interface, under Integration > SNMP Trap Administration > SNMP Trap Groups.

Figure 17. Edit Traps in Group view

For more information about how to work with SNMP traps, see Grouping SNMP Traps .

Rules

Foglight allows you to create flexible rules that can be applied to complex, interrelated data from multiple sources within your distributed system. You can associate several different actions with a rule, configure a rule so that it does not fire repeatedly, and associate a rule with schedules to define when it should and should not be evaluated.

Different types of data can be used in rules, including registry variables, raw metrics, derived metrics, and topology object properties.

There are two types of rules in Foglight: simple rules and multiple-severity rules. A simple rule has a single condition, and can be in one of three states: Fire, Undefined, or Normal. A multiple-severity rule can have up to five severity levels: Undefined, Fatal, Critical, Warning, and Normal.

Rule conditions are regularly evaluated against monitoring data (metrics and topology object properties collected from your monitored environment and transformed into a standard format). Therefore, the state of the rule can change if the data changes. For example, if a set of monitoring data matches a simple rule’s condition, the rule enters the Fire state. If the next set does not match the condition, the rule exits the Fire state and enters the Normal state.

A rule condition is a type of expression that can be true or false. When it evaluates to true, the rule is said to fire, causing any actions that are associated with the rule or severity level to be performed. You can configure a rule to perform one or more actions upon entering or exiting each state. When a multiple-severity rule fires, an alarm also appears in Foglight.

See “Introduction to Rules” and “Creating and Editing Rules” in the Foglight Administration and Configuration Guide for more information.

Alarm Integration Rule

Purpose

The Alarm Integration rule is used to forward alarms out of Foglight into a third-party system.

Although disabled by default, when enabled, it will fire for all alarms out of the box and will generate an XML document that can be fed to a script. The script defined in the action can be used to send to the third-party system.

The rule triggering is event-driven.

This rule can be viewed by opening the navigation panel, and under Dashboards, click Administration > Rules & Notifications > Manage Rules and then click on a Alarm Integration rule.

For more information about how to customize and edit the Alarm Integration rule, see Forwarding Alarms to Third-Party Systems .

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级