Serviio

I've turned on DEBUG logging to troubleshoot some intermittent issues that I need to 'watch' over a longer period of time.

the current log output's way too huge, getting filled with Library-related info, so reading


I added to


the following config


then, deleted existing LOGS and restarted Serviio.

Better, but my logs are still getting filled with irrelevant Library-related info, e.g.,


What additional filter can I add to quiet those ^^^ down?

or if you don't any debug log from the library

Hi zip,

Does this mean there are now three categories to control detailed reporting for the library:

<category name="org.serviio.library.local">
<category name="org.serviio.library.online">
<category name="org.serviio.library.dao">

to control reporting for individual components of the library, as well as the overall <category name="org.serviio.library"> if you want just to control it as a single overall entity? While the first two are self explanatory, what does the 3rd one (the .dao) control? Just trying to work out how I add this to my tool viewtopic.php?f=17&t=12136 in a meaningful way (ie. how to explain it to users). It may be easier in my tool to simply act on the entire library - its only meant to be a helper, not necessarily for advanced users/situations, but still this level of detail will be handy to update the wiki (I'll do that if you like).

It's just the way the code is packaged. So the config for .library will work with that + any sub packages (like .library.online). The .dao is just another pubpackage including code that actually talks to the database.

Cheers - have updated http://wiki.serviio.org/doku.php?id=debug_filter. Let me know if you need any changes to it.