Bug 46100 - NagiosAppender available for contribution
Summary: NagiosAppender available for contribution
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-27 13:53 UTC by Jar Lyons
Modified: 2008-10-29 16:16 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jar Lyons 2008-10-27 13:53:47 UTC
I have developed an appender that contains a pure java implementation of the nsca protocol used to send passive service checks to Nagios. (http://sourceforge.net/projects/nagiosappender/)

It has been under development off and on for a few years, and is stable.

It is currently listed as the number two appender project at sourceforge based on downloads ( > 1400).

Given that it comes with an Apache 2.0 license, I would like to suggest it be included as a core log4j distribution component.

Here is an article that describes how the appender can be best leveraged ...

http://www.novell.com/communities/node/4131/application-monitoring-made-easy-java-applications-using-nagios
Comment 1 Curt Arnold 2008-10-29 16:16:18 UTC
Any code developed outside of the ASF must be reviewed by the Incubator PMC for intellectual property issues.  The most appropriate process for this contribution is described at http://incubator.apache.org/ip-clearance/index.html.

A common concern of the ASF and the Incubator PMC in particular is that the ASF does not become a dumping ground for unsupported code.  Would you intend to be active within the log4j community and support the appender on the mailing list?

The recent trend in the project is to place appenders with dependencies on JDK 1.4 and later or other new dependencies into log4j "companions".  Whether this appender would be a candidate for inclusion in log4j proper or packaged as a companion would need to be decided on log4j-dev?