One of the improvements included in a recent patch release for Cascade Server (6.10.6) makes it easier for administrators to configure logging. Exciting, right?! Not really. By nature the feature isn't flashy and won't ever be seen by end users. In fact, some administrators may never find the need to use it. However, for administrators that do find themselves facing hard-to-diagnose problems in the system, this functionality can be a nice time saver.

Simple... except for that fact that--unless you contact us asking for help--you have no idea what to enter in that text field. You're not alone. Sometimes I don't even know what to enter into that field and I have to go digging into the back-end code to find out. Obviously that is not a great option for our clients.

Now there is no need to know or memorize all of those long and nerdy sounding class names. Instead, administrators can simply select a particular feature of the system to monitor and Cascade will automatically add the appropriate classes. By default, we've added some of the more common categories we see as being necessary and new categories will be added in the future as needed.

This little improvement will help make support interactions that require DEBUG logging much less painful for everyone. On that note, it may prevent a support interaction from ever being needed in the first place. Read more about the 6.10.6 DEBUG logging improvement in the Knowledge Base.