Stitchers not used by default
These stitchers are provided as examples of extra functionality that can be added to the Event Gateway using stitchers. These stitchers can be executed from other stitchers.
The following table describes the Event Gateway stitchers that are not used by default.
| Stitcher | Description | Expected arguments | Returns |
|---|---|---|---|
| EntityFromAtmIfDescr.stch | This stitcher illustrates how data extracted from an event (typically using the ExtractIfString stitcher) can be manipulated before looking up related topology in the NCIM cache. In this example, events are be raised with a shortened interface description, missing a standard suffix. That suffix is added before looking up the topology. | Main node name (text)
|
An interface on the given main node with
an ifDescr matching the event interface description,
concatenated with the predefined -atm subif string. |
| RetrieveAlertDetails.stch | Looks in the Object Server alert.details table for any data relating to the current in-scope event, and adds any data found to the in-scope event. Note that in this example, this is done indiscriminately and no filtering of data is performed. This also provides a template example of how to query the Object Server for additional data. | None | No return value |