
306 vFoglight
Administration and Configuration Guide
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 vFoglight: 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 vFoglight.
For more information see “Working with Rules” on page 223.
Core vFoglight rules
Rules in this section:
• Agent Health State Rule
• BSM All Events Rule
• Catalyst Data Service Discarding Data Rule
• Catalyst Database Space Checking Rule
• Catalyst Free Space Checking for Oracle Tablespaces Rule
• DiagnosticAgentDiscovery
• Email Reports Sample Rule
• vFoglight Agent Type License Checker
• vFoglight Memory Usage Check Rule
• vFoglight Topology Size Limit Reached
Kommentare zu diesen Handbüchern