-
Notifications
You must be signed in to change notification settings - Fork 28
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
Improvements in documentation regarding services #424
Comments
Date: 2012-02-10 14:41:31 I'm currently documenting Octopussy for the Company I work for. I'm gonna hand something back to you as soon as it is usable. :-] TOC: 1 General Information About the Software |
Date: 2012-02-13 01:39:40 It will be AWESOME ! It will be a good start for me to finally make a good documentation about Octopussy. Thanks for all your work in Octopussy ! |
Thanks Sebastion, it will be very nice but also hard. |
I created a new Github repository dedicated to Octopussy documentation. I opened 2 isuses from this issue: |
To ensure our recent conversation won't get lost, but may also become advantageous for someone lese in the future, I willl ist up some things I suggest for the future documentation.
Add to the documentation that "(pattern1|pattern2)" is not recommended (and why), but (?:pattern1|pattern2) is recommended instead, please. Maybe a reference to the official Perl documentation would be appropriate here as suggested.
Add to the documentation, that '(daemonname|DAEMONNAME)' is not necessary anyway because regexps are case insensitive in Octopussy (because 2 messages which are only different by their case, have the same meaning), please.
Add to the documentation that more than one <@:msg@>-tag is not recommended since it will cause problems within the repots generation of Octopussy, please.
Add to the documentation, that the ordering of patterns within a service is really important only in case one uses alert(s) and/or one activated statistics on these services and that in other cases, Octopussy generates a big global regexp with all patterns in one service. Also add a more extensive explaination of the nature of reports, please.
Add some sensible examples of generated alerts and/or wole alert classes to the documentation, please. This will ensure people understand the power and possibilities of Octopussy.
The text was updated successfully, but these errors were encountered: