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
How to unit test a class which is just an adapter that logs input and output to a third-party library?
I have the following (in C#, but the question could also apply to Java):
Event based logging. Is it a good idea and is it ok to pass a handle to a “logged” object?
Hi I have fairly complex program that is doing computations in a quite large loop. I want to log some basic statistic about the run to be able to analyze its performance over time and vs loop number. For now I am outputting a set of numbers, about 5 or 6, each loop.
Event based logging. Is it a good idea and is it ok to pass a handle to a “logged” object?
Hi I have fairly complex program that is doing computations in a quite large loop. I want to log some basic statistic about the run to be able to analyze its performance over time and vs loop number. For now I am outputting a set of numbers, about 5 or 6, each loop.
Event based logging. Is it a good idea and is it ok to pass a handle to a “logged” object?
Hi I have fairly complex program that is doing computations in a quite large loop. I want to log some basic statistic about the run to be able to analyze its performance over time and vs loop number. For now I am outputting a set of numbers, about 5 or 6, each loop.
What is the best way to track / record the current programming project you work on? [duplicate]
This question already has answers here: Where should a programmer explain the extended logic behind the code? (5 answers) Methodology for documenting existing code base (6 answers) When do you start documenting the code? [closed] (13 answers) Closed 11 years ago. I have been in this problem for long time and I want to know […]
What is the best way to track / record the current programming project you work on? [duplicate]
This question already has answers here: Where should a programmer explain the extended logic behind the code? (5 answers) Methodology for documenting existing code base (6 answers) When do you start documenting the code? [closed] (13 answers) Closed 11 years ago. I have been in this problem for long time and I want to know […]