Structure of a Rule

A rule has a number of components.

They are:

The scope: Defines the schema, cube, hierarchy, and level on which you wish to create the rule.
Set condition: This component defines the condition when you want to start monitoring the situation. You can define high or low watermarks you want to observe. For example, a hit count of a service crosses a threshold.
A set condition triggers one or more set actions.
Set action: This component defines the action you want the SPM Server to take if the set condition is met.
You can choose an email action or a log action. Or you can also select a custom action. For details on creating and configuring Custom Actions, see the TIBCO Service Performance Manager API Reference guide.
Clear condition: This component defines when you want to stop monitoring the situation. For example, the hit count of a service returns to the expected range.
A clear condition triggers a clear action.
Clear action: This component defines the action you want the SPM Server to take if the clear condition is met.
To understand how all these components define a complete rule, see the following example.