Dell Vizioncore Manual de usuario Pagina 253

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 531
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 252
Working with vFoglight Rules and Registry 253
Working with Rules
The Rule Definition tab refreshes, showing the Event Name box on the right.
2
Specify the event that you want to use as the rule trigger.
Click Event Name and select one of the following events:
AlarmSystemEvent
ReportGeneratedEvent
Note For details on how to write conditions for event-driven rules, see “Defining conditions
for event-driven rules on page 267.
From here, you can proceed to “Defining the rule scope” on page 253.
Defining the rule scope
The scope of a rule defines the set of topology objects against which it runs. A rule must
be scoped to a topology type and can optionally be scoped to specific topology objects
of that type. If a rule is not scoped to specific objects, it applies to all instances of that
type. The scope object is the object on which alarms will appear in the vFoglight
interface. The rule scope is specified using the query language.
A rule can apply to a topology type or to one or more objects of that type. You can
change the scope of a rule (the topology type or specific topology object(s) to which it
applies) after its creation.
For detail information on how to scope a rule or derived metric to one or more topology
objects, see “Using the Query Language” on page 473.
Caution You may need to reconfigure the rule’s condition(s) if you change its scope: the metrics,
registry variables, and topology object properties specified in the existing condition(s)
may not be available for the new topology type or object(s).
To get started with specifying a rule scope:
Note This procedure continues from “Triggering rules” on page 251.
Vista de pagina 252
1 2 ... 248 249 250 251 252 253 254 255 256 257 258 ... 530 531

Comentarios a estos manuales

Sin comentarios