-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
SOC-3529 add support for pd merging (#10)
* Add comment explaining how the different pieces fit together, and start renaming things to use correct terms... * Rename `zabbix_get_event_id` to `zabbix_get_Event_id_from_pd_object` and (try to) make it smart enough to pull an eventid from either an alert or an incident. * Minimum viable code (it ACK'd two zabbix events that were part of a single merged PD incident). * Attempt to fallback to old mechanism if /alerts end-point didn't work... * It actually works now. Merges the events properly in Zabbix. - Switched JSON encoding to using a JSON object instead of imported `to_json` so can "allow_blessed" for all json stuff. - Added a bunch of debugging stuff, including every func outputting its arguments on every call if DEBUG>=5. - Added logic and a couple functions for merging Zabbix events when PD incidents merge. * Style fixups with `perltidy` * Another pass with (newer version of) `perltidy`. * Add a dependency blocking LWP from installing on perl 5.10 pipeline * Try to get a lower version of a dependency module when compile testing for perl 5.10 * Added configurable option for how to handle incoming merge events * Update documentation and example config to reflect feature changes. Also a bit of just general docs/example improvements while I was in there. * Minor `perltidy` fixes. * Remove the attempt to validate the pdmergeaction option; it wasn't working and doesn't add enough value to be worth digging into further (anything other than `merge` or `resolve` gets treated same as `ignore`). And a tiny bit more debugging. * Minor formatting fixup via `perltidy`
- Loading branch information
1 parent
90405db
commit 01c3955
Showing
4 changed files
with
265 additions
and
97 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.