Page 1 of 1

Can one have more detailed control over logging??

PostPosted: Sun Nov 24, 2013 7:39 pm
by n3mmr
All I know about is a total debug log, and how to take library stuff away from that log.

Is there any way to set up logging in a more detailed way?

I'd like to have detailed debug logging, but only for a short time after a specific trigger; i e for maybe 1-5 minutes after I try to play one specific online resource.

Or maybe detailed logging for anything that accesses resources on a specific set of URLs.

I have a problem where a set of online resources flicker on and off at irregular intervals; first you can play them, maybe for 10 minutes or a few hours, then they won't play: I e, they ALMOST play, there's a duration known to the player, but then it all just dies. After a few hours, things play nicely again.

Re: Can one have more detailed control over logging??

PostPosted: Mon Nov 25, 2013 7:19 pm
by zip
No, that is not currently possible, unless I write some code to do that - which I will not ;-)

There are some Notepad+ highlighters on the forum to at least make the log file more readable.

Re: Can one have more detailed control over logging??

PostPosted: Wed Nov 27, 2013 11:31 am
by n3mmr
zip wrote:No, that is not currently possible, unless I write some code to do that - which I will not ;-)

There are some Notepad+ highlighters on the forum to at least make the log file more readable.

I CAN understand your reluctance to do that.

However, the size of the logs isn't actually the problem, it's that there's a delay added when the logs are too detailed, and that sometimes seems to defeat the problem.

Ah well, the problem I was trying to look at right now went away, and I do have a guess at what the problem was. But I don't know for sure, and having more debug log control would have helped.

Re: Can one have more detailed control over logging??

PostPosted: Wed Nov 27, 2013 1:23 pm
by Illico

Re: Can one have more detailed control over logging??

PostPosted: Thu Nov 28, 2013 8:12 am
by n3mmr
Illico wrote:http://wiki.serviio.org/doku.php?id=debug_filter


I was aware of that, I was after other kinds of triggers, further types of log, even external triggers.

The problem did go away. Next time something happens I'll be better prepared for debugging in other parts of the network equipment.