BrunoBonacci
commented
4 years ago Hi Darin,
In my design, the core should have zero dependencies to avoid conflicts as much as possible. At the moment has only the ring-buffer which I'm thinking to embed.
Adding Json formatter to the console printing would require cheshire (or similar) which in turn would add jackson which is a very popular library and very likely to conflict with other dependencies in your projects.
Minimising the risk of dependency clash is a primary design goal for this library, this is the reason why I haven't added this feature in the ConsolePublisher.
Another aspect is that the Console publisher is designed for development purpose only. In the past, I had issues with a similar setup of yours and I've experienced the loss of data. High-volume systems which produce loads of logs could cause the system to discard as much as 40-60% of logs because they can't keep up with the collection, parsing and indexing. The problem was fixed by publishing directly to the end system.
For example, in your case, you could write a simple publisher which sends the data directly to Sumologic HTTP endpoints and takes advantage of batching apis.
Alternatively, if you think that it is still preferable to log to the console, I would recommend writing a custom publisher as described here: How to write custom publishers. Basically, you can take the first example and add the JSON formatting. To start your new publisher you can use the Custom publishers which dynamically loads the publisher or the Inline publishers config.
If this is something that many people require I could think of adding this to the Advanced Console publisher which it would be separated from the core.
bn-darindouglass-zz
Apps in Kube tend to print their logs to stdout which allows Kube to handle logging in a centralized way. Many log aggregation services can query these logs and ingest them into their system. If these logs are in JSON format, the services (e.g. sumologic) automatically decode them and make their fields available for consumption in their app.
It would be an improvement if
mulogprovided a way to print JSON logs to the console. Adding a:format :edn|:jsonconfig (or similar) to theConsolePublisherwould be one way to provide this in common code and not require a new, custom publisher.