Repository navigation
NMS-8517: Notification docs - #9003
Merged
Merged
Conversation
Only the scripting, ticket, and webhook strategies had pages; JavaMail, browser, HTTP, SNMP trap, and null were undocumented or only shown by example. The pages follow the strategy classes in opennms-services and the shipped notificationCommands.xml and javamail-configuration.properties.
The docs did not explain how notifd matches events to notifications, what match-all does, or how auto-acknowledge rules and resolution notices behave. The text follows BroadcastEventProcessor, NotificationManager, and the notifd-configuration.xsd model and shipped defaults.
Adds a PagerDuty Events API v2 example to the webhook strategy page, with trigger and resolve commands tied together by a dedup key. It uses only the existing WebhookNotificationStrategy switches and notification parameters.
…fic users The reference material for rules, groups, and destination paths existed, but nothing showed how to combine them for this common task. The procedure uses the filter rule syntax in JdbcFilterDao and the shipped notifications.xml and notifd-configuration.xml defaults.
This was referenced Oct 22, 2026
dino2gnt
requested changes
Oct 22, 2026
|
|
||
| Discord replies with `204` and an empty body on success. | ||
|
|
||
| [[pagerduty]] |
Contributor
There was a problem hiding this comment.
I don't agree with documenting this in detail at this location. We have a PagerDuty plugin that handles all this transparently.
Contributor
There was a problem hiding this comment.
Agreed. We don't want PagerDuty here for webhooks. I tried to leave the examples here as mostly generic as possible.
Contributor
Author
There was a problem hiding this comment.
Removed in 2f13cab, which reverts the PagerDuty commit; webhook.adoc is back to its develop content.
marshallmassengill
requested changes
Oct 22, 2026
marshallmassengill
left a comment
Contributor
There was a problem hiding this comment.
Other than the pagerduty thing, this is good I think.
This reverts ee59bc1. PagerDuty is covered by the PagerDuty plugin, and the webhook page keeps its examples generic, so webhook.adoc is back to its develop content.
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the notification strategies and routing, split out of #8984; content checked against the code on develop, one commit per ticket.
operation/…/notifications/strategies/{javamail,http,snmp-trap,browser}.adoc(new),commands.adocopennms-services/…/notifd/*NotificationStrategy.java,notificationCommands.xmloperation/…/notifications/concepts.adoc,reference/…/notifd.adocBroadcastEventProcessor.java,NotificationManager.java,notifd-configuration.xsdoperation/…/notifications/route-by-node.adoc(new)JdbcFilterDao.javaThe SnmpTrap command example is also corrected.
Not addressed
The docs build adds no warnings (develop's two existing ones remain).
External References