SUPPORT 3.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. FORUMS SUPPORT
  2. --------------
  3. Even though the mailing list are still used for support, the forums are
  4. by far the fastest and best way to receive support these days.
  5. General plugin usage and Nagios integration questions can be posted at:
  6. http://support.nagios.com/forum/viewforum.php?f=7
  7. Bug reports and development queries should be posted to the development
  8. forums:
  9. http://support.nagios.com/forum/viewforum.php?f=35
  10. The mailing lists are still alive and you are welcome to post your
  11. questions to the list if you are inclined to do so:
  12. MAILING LIST SUPPORT
  13. --------------------
  14. Using the mailing lists and tracker databases at SourceForge are the
  15. best ways to obtain direct support for the Nagios Plugins. There may
  16. also be commercial support options available to you -- check
  17. http://www.nagios.org/ to track the current status of commercial
  18. support offerings.
  19. There are two mailing lists associated with Nagios Plugin development:
  20. 'help' (mailto:help@nagios-plugins.org), and 'devel'
  21. (mailto:devel@nagios-plugins.org). Unless you are fairly
  22. certain you have found a bug or that you are requesting a new feature,
  23. please direct support requests to 'help'.
  24. Because these lists are handled entirely by volunteers, and because
  25. these same volunteers are often plugin developers who can also use
  26. their time to fix bug and provide feature requests, it is generally in
  27. you interest to do a modest amount of legwork before posting to either
  28. of these lists.
  29. Plugins that are in the contrib directories are provided as-is. We will
  30. try to help, but sometimes the plugins have dependencies that the
  31. nagios-plugin developers do not have access to. You may be able to try
  32. the authors directly.
  33. In brief, always provide the version of the software that you are
  34. using, and when requesting features or reporting bugs, first check to
  35. see that the issue has not already been addressed in the current Git
  36. code.
  37. GETTING HELP
  38. ------------
  39. Requests to 'help' require posting the version number of the
  40. plugin. The best place to include the version information is in the
  41. subject. A good post would have a subject like:
  42. Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12
  43. If you do not include the version of the plugin, you risk having your
  44. post silently ignored.
  45. Be advised that the core plugins (and in fact many of the contributed
  46. plugins) will provide a description of their use when invoked with the
  47. '--help' option. Please read the help carefully and in it's entirety
  48. before asking for support.
  49. REPORTING BUGS AND SUBMITTING PATCHES
  50. -------------------------------------
  51. Bug reports, investigations of possible bugs, feature requests, and
  52. patch submissions should be submitted to the development list at
  53. mailto:devel@nagios-plugins.org. Please raise an issue first in
  54. GitHub, otherwise your email is likely to be missed over time.
  55. You should identify the version, preferably in the subject line.
  56. However, to best use developer resources, it is suggested that you
  57. reference your report to one of the following sources:
  58. 1) The most recent release, including beta's
  59. 2) The current snapshots (there's a link provided on
  60. https://www.nagios-plugins.org/download.html)
  61. 3) The current Git code from GitHub
  62. (This does not mean you should run any of these sources in a
  63. production environment - the latter two you clearly should
  64. not. However, if you find a bug, you should determine whether it is
  65. still present in one of these sources, preferably either (2) or (3)
  66. which are most recent.)
  67. From experience, I know that most bugs can be fixed with only a few
  68. more moments work than it takes to determine if the bug is still
  69. present in the Git tree. If you can save a developer the expense of
  70. that time, you ensure that bugs are fixed more rapidly, and thus you
  71. ensure your problem resolution is reflected in a stable release more
  72. quickly.