Additional library-related log filters needed

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

  Code:

   http://wiki.serviio.org/doku.php?id=detail_logging
   http://wiki.serviio.org/doku.php?id=debug_filter


I added to

  Code:

   config/log4j.xml


the following config

  Code:

   ...
   <category name="org.serviio">
      <priority value="DEBUG"/>
   </category>

   <category name="org.serviio.library.local">
      <priority value="INFO"/>
   </category>

   <category name="org.serviio.library.online">
      <priority value="INFO"/>
   </category>
   ...


then, deleted existing LOGS and restarted Serviio.

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

  Code:

   ...
   2013-08-24 15:56:46,086 DEBUG [MediaItemDAOImpl] Checking if DB already contains media item /mnt/Video/TV/tvshow/Season2/tvshow - 2x10 - ep name.mkv
   2013-08-24 15:56:46,086 DEBUG [MediaItemDAOImpl] Looking up a media item for file path: /mnt/Video/TV/tvshow/Season2/tvshow - 2x10 - ep name.mkv, ignore case: false
   2013-08-24 15:56:46,086 DEBUG [MediaItemDAOImpl] Media item /mnt/Video/TV/tvshow/Season2/tvshow - 2x10 - ep name.mkv already exists in DB
   2013-08-24 15:56:46,083 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 222) and extractor XBMC
   2013-08-24 15:56:46,087 DEBUG [MetadataDescriptorDAOImpl] Reading MetadataDescriptor for MediaItem (id = 222) and extractor COVER_IMAGE_IN_FOLDER
   2013-08-24 15:56:46,089 DEBUG [MediaItemDAOImpl] Getting file of media item 223
   ...


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

[zip]

  Code:

<category name="org.serviio.library.dao">
      <priority value="INFO"/>
</category>

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

  Code:

<category name="org.serviio.library">
      <priority value="INFO"/>
</category>

[DenyAll]

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).

[zip]

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.

[DenyAll]

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