NLog has an internal log that the developer can use to troubleshoot issues with logging. Does Enterprise Library Logging have anything like that that I can use to figure out why my log messages aren’t going anywhere?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
NLog has an internal log that the developer can use to troubleshoot issues with logging. Does Enterprise Library Logging have anything like that that I can use to figure out why my log messages aren’t going anywhere?
There’s a “Logging Errors and Warnings” special category. If there’s a problem with the logging infrastructure itself, it’ll get logged there. You can point this at any trace listener – by default it goes to the Windows event log.
Of course, if you have a problem with the trace listener for the errors, things get lost. There’s only so many turtles you can stack on this one.