Logging Services employ many public and private support channels for users, contributors, and maintainers.

Important

The Apache Software Foundation does not employ individuals to develop and support any of its projects. The individuals who contribute to Apache projects do it either as part of specific tasks assigned to them by their employer, on their own initiative to benefit their employer, or on their own free time.

User support

If you have questions like:

  • "How do I configure Log4j with the file appender?"

  • "My Log4Net layout is not working as expected; what should I do?"

  • "How can I migrate from Log4j 1 with this custom configuration?"

We urge you to first check the website of the associated project to see if your question has already been answered there. If not, you can use one the following communication channels:

  • GitHub Discussions (Log4cxx, Log4j, Log4net)

  • log4j-user@logging.apache.org mailing list (subscribe | unsubscribe | post | archive)

    Warning

    You are expected to be subscribed to a mailing list to receive replies to your posted questions! If you are not subscribed, when you post an email, it will be subject to moderation (hence, will be distributed with a delay) and the only way you would be able to follow the conversation is to use the mailing list archive.

    Warning

    Messages sent to a public mailing list will be seen by many people and also re-published by 3rd party websites. It is usually not possible to remove them. Please don’t send mails containing confidential information to public mailing lists. For more information, please see the privacy policy

  • Stack Overflow (Log4cxx, Log4j, Log4net)

Maintainer discussions

If you have questions or feedback like:

  • A class should be public instead of package-private

  • A plugin is missing configuration options

  • You’ve found a bug

  • You have questions that are not project-specific

then please contact us using the following channels:

  • GitHub Discussions (Log4cxx, Log4j, Log4net)

  • dev@logging.apache.org mailing list (subscribe | unsubscribe | post | archive)

    Warning

    You are expected to be subscribed to a mailing list to receive replies to your posted questions! If you are not subscribed, when you post an email, it will be subject to moderation (hence, will be distributed with a delay) and the only way you would be able to follow the conversation is to use the mailing list archive.

    Warning

    Messages sent to a public mailing list will be seen by many people and also re-published by 3rd party websites. It is usually not possible to remove them. Please don’t send mails containing confidential information to public mailing lists. For more information, please see the privacy policy

  • #logging Slack channel (exclusive to committers)

Private discussions

Users are strongly advised to use one of the above public channels. If it deems necessary, use following channels for private discussions.

  • security@logging.apache.org mailing list (post) is used for reporting unlisted security vulnerabilities or other unexpected behaviour that has a security impact. Make sure to check the Security page before sending an email.

  • private@logging.apache.org mailing list (post) is used for discussing other confidential topics with the Logging Services PMC.

  • #logging-pmc Slack channel (exclusive to committers)

Issues

Logging Services projects use GitHub Issues (Log4cxx, Log4j, Log4net) as their issue tracking system. The old issue tracking system, JIRA (Log4cxx, Log4j), is still accessible, though only recommended for issues that were already created there. For issues that are not project-specific, get in touch with maintainers instead.

Issues get resolved in one of the following ways:

  1. The reporter or another interested party provides a pull request tagging the issue in its title

  2. A committer is interested in the issue and decides to work on it

  3. The reporter or another interested party sponsors one or more of the committers listed below to encourage them to work on the issue

Created issues are subject to the following policy:

Quality

Issues posted of insufficient quality will be removed

No protracted discussions

Issues likely to result in protracted discussion must be posted to the mailing lists

No Questions

Do not post questions as issues! These will be removed, and you will be asked to post questions to the mailing lists instead.

Sponsorship

Sponsorship can be used simply as a way to say thank you for the work that has been done or as a way to encourage specific issues to be worked on. In either case, while the Apache Logging Services project thanks you for your support, we cannot be responsible for any promises and/or contributions made by an individual committer, as individual commits must be reviewed and accepted by the project team.

Sponsors

There are a handful of tools that developers in the community use; some are open-source and some are commercial. We would like to take this opportunity to thank our sponsors providing the project maintainers access to these tools:

There are several sponsors supporting ASF.

Third-party commercial support

While neither the Apache Software Foundation nor the Apache Logging Services project provide any commercial support for the Logging Services products, individual committers may collaborate with services that provide such support.

The following aims to be a list of all commercial support services involving one or more Logging Services PMC members.

Abstract Dynamics

Consultancy services offered by PMC member Volkan Yazıcı

Copernik

Consultancy services offered by PMC member Piotr Karwasz

Grobmeier Solutions

Consultancy services offered by PMC member Christian Grobmeier

Tidelift

Some Log4j maintainers receive funding from Tidelift for their maintenance efforts.