问题
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?
回答1:
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.
来源：https://stackoverflow.com/questions/6336595/does-el-logging-have-a-troubleshooting-tool-like-nlog-internal-log