Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Monitor adapter events

Monitor adapters generate events for specific occurrences of detected actions in external systems. The criteria for event generation are defined in the adapter's configuration node in Grid Manager. Monitor adapters generate events when they are enabled on an active peer and an external incident occurs that warrants an event notification.

The following figure shows a sample event for a monitor adapter.

XML sample of a monitor adapter event

<adapter-event>
 <source-adapter>adapter-name</source-adapter>
 <event>event text</event>
 <data>event XML data</data>
</adapter-event>

Each adapter event contains XML elements as indicated in the following table.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

Note

To use the data from a monitor adapter event in the triggered process, a Job Input Parameter, inputevent must be created on the Start activity of the process. The <data> element from the monitor adapter event populates this input. For more information, see Creating rules in the BMC Atrium Orchestrator Platform online documentation.

Rules are created in BMC Atrium Orchestrator Development Studio, within the rules designer for a module, to evaluate these events. For monitor adapter events that meet the module's rule criteria, a process is triggered. 

For detailed instructions for creating rules for a module, see Overview-of-creating-the-workflows. 

 

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