-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create advanced-alarm-handling.adoc #7426
base: develop
Are you sure you want to change the base?
Conversation
Adding a page for examples of advanced alarm handling with drools.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a great start.
docs/modules/operation/pages/deep-dive/alarms/advanced-alarm-handling.adoc
Outdated
Show resolved
Hide resolved
docs/modules/operation/pages/deep-dive/alarms/advanced-alarm-handling.adoc
Outdated
Show resolved
Hide resolved
…andling.adoc Co-authored-by: Dino <dyancey@opennms.com>
…andling.adoc Co-authored-by: Dino <dyancey@opennms.com>
What is this |
Ugh... yeah... will resolve that tomorrow. |
@marshallmassengill you may have to merge latest develop into your branch to make the circleci pass the builds |
I think I've done that? |
Adding a page for examples of advanced alarm handling with drools.
All Contributors
Contribution Checklist
Once there is an issue, please:
${JIRA-ISSUE-NUMBER}: subject of pull request
Don't worry if this sounds like a lot, we can help you get things set up properly.
-smoke
in it to trigger smoke tests?foundation-*
branch, does it try to avoid changing files in$OPENNMS_HOME/etc/
?What's Next?
A PR should be assigned at least 2 reviewers. If you know that someone would be a good person to review your code, feel free to add them.
If you need help making additions or changes to the documentation related to your changes, please let us know.
In any case, if anything is unclear or you want help getting your PR ready for merge, please don't hesitate to say something in the comments here,
or in the #opennms-development chat channel.
Once reviewer(s) accept the PR and the branch passes continuous integration, the PR is eligible for merge.
At that time, if you have commit access (are an OpenNMS Group employee or a member of the OGP) you are welcome to merge the PR when you're ready.
Otherwise, a reviewer can merge it for you.
Thanks for taking time to contribute!
External References