Wikis - Page

Using a flow trigger script, has anyone found a clean way of enriching NNMi incidents with flow data without the incident been registered

0 Likes

For most flows, what we are doing is letting NNMi or NA detect incidents such as threshold violations, config changes, etc... and then have NNMi trigger a flow when the incident turns to the "registered" lifecycle with an action through a script, the limitation is that when these flows collect/generate data, then enrich the NNMi incident with that data, that incident has already been forwarded to other tools.

Our workaround for the above is to create a whole new trap with the original data plus the data from the flow.

Has anyone found a clean way of using OO flow data to enrich NNMi/OpsBridge incidents in one go, have only the original incident with all the enriched data?

Labels:

Events
How To-Best Practice
Support Tips/Knowledge Docs
Comment List
  • Not sure if anyone found a better way, but here's what we did.

    We set a few minutes of dampening for NA traps(note we're only using this NA/NNMi feature for config changes) then I set a custom rule in NA to send out a second trap for config changes with a slightly different message and used payload filters to have this second trap trigger our flow which will enhance the original trap while it's dampened and move it to "Registered" state once ready at which point it will be forwarded to OBM.

    Obviously, there are logics in place behind the flow but those can probably be accommodated to your environment.

Related
Recommended