Cross-launch

it is possible to configure custom actions to ease the creation of DDA entries based on events  selected in an event table report.

When configured, the cross-launch will lead the user into the “add entry” dialog of an existing Data Editor module, with DDA slots pre-filled using hardcoded or slot values from the selected event.

The crosslaunch capability is configured in the QuickQueries module configuration file, in the section [Custom]. Note that this section does not exist by default.

Example :

A DAModifier module named “EventEnrichment” is created. It is used to manage the table EVENT_ENRICHMENT. This table has the following definition :

 

MC_DATA_CLASS :

HOST_ENRICHMENT ISA DATA

DEFINES

{

     Class: STRING,key=yes;

     Host: STRING,key=yes;

ObjectClass: STRING, key=yes;

Parameter: STRING,key=yes;

Environment: STRING;

     Site: STRING;

};

END

 

To enable the creation of entries in that DDA table based on events reported in ProactivePack, we will create the following section in QuickQueries.conf

[Custom]

CustomActions="CreateEnrichment"
CreateEnrichment="new_data:EventTreshold"
CreateEnrichmentMap="Class:slot.class,Hostl:slot.mc_host,ObjectClass:slot.mc_object_class,Parameter:slot.mc_parameter,severity:slot.severity,Enviromment:PRODUCTION,Site:HQ"

Where:

-          "CustomActions=<ActionName>" lists the actions (comma separated) in the context menu. In this example we only have one action “CreateEnrichment”.

-          <ActionName>=new_data:<ModuleName> describes, for each <ActionName> defined in CustomActions, which Data Editor module should be used. new_data: is a fixed keyword

-          <ActionName>Map=<comma separated list of key value pairs>. Provides the mapping directives from event slots into DDA slots :
< DDA slot name>:"Fixed value" - to provide a fixed value
< DDA slot name>:slot.<event slotname> - to provide the value of an event slot.