Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why does Log4net input require changes to logging code?
See original GitHub issueAs far as I see (all?) input libraries are written in such a way that they can read from their respective inputs without requiring any changes to the existing log writing code. Only log4net input is different. Here we are required to request a logger from a specific logger repository called EventFlowRepo. Existing log4net logging code won’t work, because it typically creates loggers from the default repository.
Why is log4net input implemented in this way? Can it be changed? Can it be used differently so that it behaves like other inputs (i.e. no changes to existing logging code are required).
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It is a little fuzzy, but I remember having issues if I did not create a named repository. I don’t think this is necessary, but I am unsure. It was just inexperience on my part I believe.
I will take a deeper look into it over the weekend, if you do not beat me to it.
It should be fairly easy to fix this. One possibility is to make the logging repository name a configuration parameter and use the value of the parameter as part of initialization Default value could be empty, which would be a hint to use the default repository.
@jeremysmith1 was there a particular reason why you used a named repository as the default for log4net input?