Why not just contribute to log4js-node ?

We’re hoping Logjack will become a “foundation component” for Hubrix — that is, the logging subsystem for Hurima and all our future products. Our needs differ somewhat from those of the broader DevOps community, and we don’t want to “drag” log4js-node in a direction that doesn’t necessarily serve the common good. To put it another way, we want “roadmap independence” for our logger.

That said, we’ll work closely with log4js-node contributors to merge any generally-useful features we develop in Logjack back into the log4js-node project, on a case-by-case basis. We’re also exploring a refactoring of Logjack as a log4js-node extension, rather than a stand-alone logger class (that depends on log4js-node anyway). But we want to go further down our roadmap before making that decision.

Logjack’s roadmap and future

Logjack is not a Hubrix “product” in the usual sense. It might become one someday, but for now, it’s just a very modest contribution to the Open Source community that has given us so much.

We don’t expect anyone to need paid support for Logjack, but if you need it for any reason, please contact us and we’ll work something out.

If we ever “promote” Logjack to full-product status, it will remain an open-source project.

Our development priority is Hurima so we’re not setting deadlines on future releases of Logjack just yet. But we already know some of the key features in our development roadmap:

API Authentication / token support (required for other features below)

Support for an “audit” logLevel — sort of like “trace” but reserved for Analytics use cases