Hi, since I found this feature in Jira Id like to abuse it if possible :)

Please vote for these if you find them useful.

I've also spend quite a bit of time extending log4j (which was a pia to 
configure the xml) to build a complete W3C extended log format access 
logging system to model Wowza and FMS.

ie

log.appstart(hashmap);
log.appstop(hashmap);
log.play(hashmap);
log.stop(hashmap);

custom levels used within the custom log methods, which also defines the 
stream x-event  and x-category ;) The cool thing about this is if 
multiple events and categories are added, in something like LogParser it 
can query a log like WHERE x-event="stop" AND x-category="stream".

W3CLevel.PLAYBACKSTOP

custom layout to produce the W3C extended format.


If people are interested in a jar to check if out let me know, there is 
always room for improvement, IE i'm not a java guy so someone may point 
out bits in the code which wont perform so well under load and under 
threading etc.

Stats logging bean on stream events (makes it a configurable plugin for 
a webapp like with wowza) -

http://jira.red5.org/browse/APPSERVER-140

Ability to get stats on the vod subscribed file -

http://jira.red5.org/browse/APPSERVER-149

Bug in playliststreamsubscriber preventing getStatistics() to return any 
data.

http://jira.red5.org/browse/SN-47

_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to