Best Creational Pattern for loggers in a multi-threaded system?
This is a follow up question on my past questions :
Concurrency pattern of logger in multithreaded application
Logging in JSON Effect on Performance
I see more and more articles about logging in JSON. You can also find one on NodeJS blog. Why does everyone like it so much? I can only see more operations getting involved:
Exception Handling Frequency/Log Detail
I am working on a fairly complex .NET application that interacts with another application. Many single-line statements are possible culprits for throwing an Exception and there is often nothing I can do to check the state before executing them to prevent these Exceptions.
What is the correct way to handle debug output in Java?
As my current Java projects grow bigger and bigger, I feel a likewise growing need to insert debug output in several points of my code.
Strategy for clients to retrieve real-time log from HTTP server
I have an HTTP Server Service application which has its own logging mechanism. It’s written in Delphi. I would like to provide a way for multiple clients to connect to this service and get a real-time update of the log. The log in the service moves rather fast, there’s a lot of things to log. There may be up to 50 messages within 1 second at times. The existing log which is already implemented is not saved, it’s only kept in the memory of the server service – where I will need to distribute it to any client which needs it. Once all clients have a log message, it should be deleted.
Opinions on logging in multiprocess applications
We have written an application that spawns at least 9 parallel processes. All processes generate a lot of logging information.
Design patterns to avoiding breaking the SRP while performing heavy data logging
A class that performs both computations and data logging* seems to have at least two responsibilities. Given a system for which the specifications require heavy data logging, what kind of design patterns or architectural patterns can be used to avoid bloating all the classes with logging calls every time they compute something?
What factors should I consider when logging a (JSF) web-app?
I’ve recently read the article The Problem with logging and was wondering about my current logging strategy.
Usualy I use Log4J in my projects and just have to decide which line/attributes I would like to log.
This strategy worked well for me in the past for all my projects without user-interaction.
Is it fine to use logs in the Helper Methods?
I have been doubting for a long time whether or not to have a logger in methods (usually helper methods) like the one below.
Log design approach
Logging was always a nightmare for me! Now I have to implement it again for a proxy system.
In this proxy application, some systems ask proxy system to call some other services.
What I have to log is