On 14/07/2006, at 10:02 AM, electroteque wrote:
well, create logs directory and file will be there (relative from
where you are running your application from,
so if you are running it from foo\bin directory, create logs folder in
there, foo\bin\logs)
Hi, it seems thats the logs were being stored in Red5/bin not myapp/bin or whatever and it would be nice if they were stored in myapp/logs not myapp/bin/logs. Anyway here is my updated log4j config, notice the escape slash it seems it needs to give a full directory path, it ended up storing the logs in the root of the drive not in the directory.
log4j.rootLogger=DEBUG, A
log4j.appender.A=org.apache.log4j.DailyRollingFileAppender
log4j.appender.A.File=E:\Red5_Logs\\Demo.log
log4j.appender.A.DatePattern='.'yyyy-MM-dd-HH-mm
log4j.appender.A.Threshold=INFO
log4j.appender.A.layout=org.apache.log4j.PatternLayout
log4j.appender.A.layout.ConversionPattern=[%p] %r %t:( %c{1}.%M ) %m %n
The problem I face now is that my Demo.log is now getting log messages from the Red5 server for everything including startup and shutdown messages for the other applications etc. And I still havent managed to work out how to create a space delimited W3C format log with detailed information about the client, FMS seems to have the exact logging setup like with windows media here is some info about it , one tags lets you choose which events to log which go into
<!-- The following describes which events to be logged. The various events -->
<!-- are as follows, -->
<!-- Event Name Category -->
<!-- ========== ======== -->
<!-- 1. connect-pending session -->
<!-- 2. connect session -->
<!-- 3. disconnect session -->
<!-- 4. publish stream -->
<!-- 5. unpublish stream -->
<!-- 6. play stream -->
<!-- 7. pause stream -->
<!-- 8. unpause stream -->
<!-- 9. seek stream -->
<!-- 10. stop stream -->
<!-- 11. record stream -->
<!-- 12. recordstop stream -->
<!-- 13. server-start server -->
<!-- 14. server-stop server -->
<!-- 15. vhost-start vhost -->
<!-- 16. vhost-stop vhost -->
<!-- 17. app-start application -->
<!-- 18. app-stop application -->
<!-- The desired events are specified as a semi-colon separated list. -->
<!-- Specifying * will log all events. -->
<Events>connect;disconnect;play;pause;unpause;stop</Events>
<!-- The following describes what information gets logged for each event. -->
<!-- Not all fields make sense for all events in which case they will be -->
<!-- empty in the log file. The possible fields are, -->
<!-- 1. x-event Type of event -->
<!-- 2. x-category Event category -->
<!-- 3. date Date at which the event occurred -->
<!-- 4. time Time at which the event occurred -->
<!-- 5. tz Time zone information -->
<!-- 6. x-ctx event dependant context information -->
<!-- 7. x-pid server process id -->
<!-- 8. x-cpu-load cpu load -->
<!-- 9. x-mem-load memory load (as reported in getServerStats) -->
<!-- 10. x-adaptor adaptor name -->
<!-- 11. x-vhost vhost name -->
<!-- 12. x-app application name -->
<!-- 13. x-appinst application instance name -->
<!-- 14. c-ip client ip address -->
<!-- 15. c-proto connection protocol - rtmp or rtmpt -->
<!-- 16. s-uri uri of the fms application -->
<!-- 17. c-referrer uri of the referrer -->
<!-- 18. c-user-agent user agent -->
<!-- 19. c-client-id client id -->
<!-- 20. cs-bytes bytes transferred from client to server -->
<!-- 21. sc-bytes bytes transferred from server to client -->
<!-- 22. x-sname stream name -->
<!-- 23. x-file-size stream size in bytes -->
<!-- 24. x-file-length stream length in seconds -->
<!-- 25. x-spos stream position -->
<!-- 26. cs-stream-bytes stream bytes transferred from client to server -->
<!-- 27. sc-stream-bytes stream bytes transferred from server to client -->
<!-- 28. s-ip ip address[es] of the server -->
<!-- 29. x-duration duration of an event/session -->
<!-- 30. x-status status code -->
<!-- 31. cs-uri-stem stem of s-uri -->
<!-- 32. cs-uri-query query portion of s-uri -->
<!-- 33. x-sname-query query portion of stream uri -->
<!-- 34. x-file-name Full file path of recorded stream -->
<!-- 35. x-file-ext stream type (flv or mp3) -->
<!-- 36. x-suri-query Same as x-sname-query -->
<!-- 37. x-suri-stem cs-uri-stem + x-sname + x-file-ext -->
<!-- 38. x-suri x-suri-stem + x-suri-query -->
<!-- 39. x-sc-qos-bytes bytes transferred from server to client for quality of service -->
<!-- The field specification is a semi-colon separated list of one or more -->
<!-- and the special key word * indicates that all fields are to be logged. -->
<!-- When customizing the fields to be logged, it is strongly recommended -->
<!-- to always at least log the type, category, date and time fields. -->
<Fields>x-category;x-event;date;time;x-pid;c-ip;cs-bytes;sc-bytes;x-sname;sc-stream-bytes;x-file-size;x-file-length</Fields>
They get logged to an access, event log respectively.
Field layout is like
#Fields: x-category x-event date time x-pid c-ip cs-bytes sc-bytes x-sname sc-stream-bytes x-file-size x-file-length x-comment
Is this possible at all ?
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
