does EL Logging have a troubleshooting tool like Nlog internal log?

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 lo开发者_StackOverflow中文版g 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.