Dynamic data


Dynamic data is similar to a small database within the cell. Dynamic data functions as contextual variables that can provide data values to rules and policies during event processing. By using dynamic data, you can create generic event management rules and policies that apply broadly. This greatly simplifies the creation and maintenance of event management rules.

For example, without using dynamic data, if you want to change the severity of an event based on the host name of a device, you must create a rule for each host name.

By using dynamic data, you can define the host names and corresponding severity as data instances and reference them from one generic rule, rather than writing one rule for each possible host name.

To define a dynamic data instance, you must first define a new data class. You can use the Dynamic Data Editor to define data class instances for use in event management rules or service models. As new hosts are added to the environment, you can add new data instances dynamically by using the CLI or an API, or through event management rules themselves. You do not need to recompile event management rules to use new data instances.

Dynamic data is stored in the event repository and updated whenever the context changes while the cell is running.

For more information about dynamic data, data classes, and the Dynamic Data Editor, see  and Navigating-the-Dynamic-Data-Editor.

 

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*