Nms testEvent: Difference between revisions
mNo edit summary |
m (→Event Replay) |
||
| Line 3: | Line 3: | ||
Better support in UI to follow mapping paths. Right now replay is specific to snmptrap. This is going to be the most common use case, however right now the TFE is doing direct DB inserts. This needs to be API calls only so we have ONE path for mapping validation, etc. | Better support in UI to follow mapping paths. Right now replay is specific to snmptrap. This is going to be the most common use case, however right now the TFE is doing direct DB inserts. This needs to be API calls only so we have ONE path for mapping validation, etc. | ||
* (07-01-2023) This has been updated to support ALL events going to the Event Engine (EE). '''All events go through a mapping process.''' | |||
* In traps, the oid for the trap is the regex for a match | |||
* in service checks the checkName is the regex for a match | |||
* if there is not something defined the catchall '*' matches and it comes in as "unmapped" and requires a human to set defaults and the match name with the replay UI. | |||
* adhoc PHP code is permitted in the PreTransform and PostTransform sections of the mapping. However only PreTransform is currently active. This should support 99% of all use cases. | |||
==== flow ==== | ==== flow ==== | ||
| Line 19: | Line 25: | ||
the snmptrap.php is going to have to be rewritten to do this work via API calls. Nothing except the API should be talking to the database. | the snmptrap.php is going to have to be rewritten to do this work via API calls. Nothing except the API should be talking to the database. | ||
As of 07-07-2023 The new snmptrap.php (Called PdoTrapReveiver.php) has been re-written to use API calls, and is stable). Logic remains the same, although | As of 07-07-2023 The new snmptrap.php (Called PdoTrapReveiver.php) has been re-written to use API calls, and is stable). Logic remains the same, although PostTransform is not supported yet. I still have not found a good reason for it to exist, however in other NMS tools there was a small subset of users who actually did use it. | ||
Revision as of 12:11, 14 July 2023
Event Replay
Notes on the replay of an event that was generated.
Better support in UI to follow mapping paths. Right now replay is specific to snmptrap. This is going to be the most common use case, however right now the TFE is doing direct DB inserts. This needs to be API calls only so we have ONE path for mapping validation, etc.
- (07-01-2023) This has been updated to support ALL events going to the Event Engine (EE). All events go through a mapping process.
- In traps, the oid for the trap is the regex for a match
- in service checks the checkName is the regex for a match
- if there is not something defined the catchall '*' matches and it comes in as "unmapped" and requires a human to set defaults and the match name with the replay UI.
- adhoc PHP code is permitted in the PreTransform and PostTransform sections of the mapping. However only PreTransform is currently active. This should support 99% of all use cases.
flow
snmptrap >> snmptrap receiver >> PHP controller >> mapping search by raw OID >> translate >> PreTransform >> insert >> PostTransform >> update
Inside PHP controller todo:
- trap received
- apiCall for hostExist
- apiCall for Mapping
- run Pre translation
- apiCall create event
- run Post translation
- apiCall update event
- complete
the snmptrap.php is going to have to be rewritten to do this work via API calls. Nothing except the API should be talking to the database.
As of 07-07-2023 The new snmptrap.php (Called PdoTrapReveiver.php) has been re-written to use API calls, and is stable). Logic remains the same, although PostTransform is not supported yet. I still have not found a good reason for it to exist, however in other NMS tools there was a small subset of users who actually did use it.