Have you ever tried to debug something, only to realize that the logs you need are not showing up? After some investigation, you discover that the logger configuration is not quite what you expected.
During this year’s Code Camp, I worked on making this easier to understand.
(The design and layout shown in the screenshot are still work in progress and may change)
The new logging view is available in the Engine Cockpit. It contains a table of live loggers. Loggers that have not been instantiated yet are shown with a strikethrough, making it easy to distinguish configured entries from active ones. A toggle also lets you include all Log4j loggers, and the table can be searched.
For each logger, you can see its configured and effective log level, which appenders are associated with it, and whether some settings are inherited. When available, the appender destination is shown as well. You can also change a logger’s level at runtime and reset it later.
To support this, I added functionality to the core that exposes the active Log4j state, including loggers and changes made while the engine is running.
The page is still being refined, but the foundation is now in place. Hopefully, this will make it much easier to answer the question: “Why can’t I see my logs?”
