Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- <Logger>
- <Access>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs/ in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- Access log file name, everything inside the square brackets will be -->
- <!-- substituted. -->
- <!-- Y represents Year, only YYYY is allowed -->
- <!-- M represents Month, only M or MM are allowed -->
- <!-- D represents Day, only D or DD are allowed -->
- <!-- N represents Version, there is no limit on number of N -->
- <!-- The number of each letter represents number of digits, for example -->
- <!-- April in M is 4 and in MM is 04 -->
- <FileName>access.[NN].log</FileName>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named access.01.log, -->
- <!-- access.02.log, access.03.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- access.00.log will be renamed to access.01.log and access.01.log -->
- <!-- will be renamed to access.02.log and so on until it reach the -->
- <!-- maximum history. Therefore, log file with the highest version -->
- <!-- number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- <!-- 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. s-ip ip address[es] of the server -->
- <!-- 8. x-pid server process id -->
- <!-- 9. x-cpu-load cpu load -->
- <!-- 10. x-mem-load memory load (as reported in getServerStats) -->
- <!-- 11. x-adaptor adaptor name -->
- <!-- 12. x-vhost vhost name -->
- <!-- 13. x-app application name -->
- <!-- 14. x-appinst application instance name -->
- <!-- 15. x-duration duration of an event/session -->
- <!-- 16. x-status status code -->
- <!-- 17. c-ip client ip address -->
- <!-- 18. c-proto connection protocol - rtmp or rtmpt -->
- <!-- 19. s-uri uri of the fms application -->
- <!-- 20. cs-uri-stem stem of s-uri -->
- <!-- 21. cs-uri-query query portion of s-uri -->
- <!-- 22. c-referrer uri of the referrer -->
- <!-- 23. c-user-agent user agent -->
- <!-- 24. c-client-id client id -->
- <!-- 25. cs-bytes bytes transferred from client to server -->
- <!-- 26. sc-bytes bytes transferred from server to client -->
- <!-- 27. c-connect-type type of connection received by the server -->
- <!-- 28. x-sname stream name -->
- <!-- 29. x-sname-query query portion of stream uri -->
- <!-- 30. x-suri-query Same as x-sname-query -->
- <!-- 31. x-suri-stem cs-uri-stem + x-sname + x-file-ext -->
- <!-- 32. x-suri x-suri-stem + x-suri-query -->
- <!-- 33. x-file-name Full file path of recorded stream -->
- <!-- 34. x-file-ext stream type (flv or mp3) -->
- <!-- 35. x-file-size stream size in bytes -->
- <!-- 36. x-file-length stream length in seconds -->
- <!-- 37. x-spos stream position -->
- <!-- 38. cs-stream-bytes stream bytes transferred from client to server -->
- <!-- 39. sc-stream-bytes stream bytes transferred from server to client -->
- <!-- 40. x-service-name name of the service providing the connection -->
- <!-- 41. x-sc-qos-bytes bytes transferred from server to client for quality of service -->
- <!-- 42. x-comment Comments -->
- <!-- 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;x-status</Fields>
- <!-- Delimiter is used to separate between fields -->
- <!-- Recommended: tab or ' '. If no delimiter is specified, default is tab -->
- <!-- Not Recommended: '#', because it is used as comment tag in W3C format -->
- <!-- Disallowed: ''', '"', '.', ':', '-', '\' and all alpha-numeric -->
- <!-- (a-z, A-Z, 0-9). Character ':' and '-' are not allowed because ':' is -->
- <!-- used in the time field and '-' is used in the date field and fields -->
- <!-- with empty value. -->
- <Delimiter></Delimiter>
- <!-- This is an optional flag to control if the fields need to be quoted -->
- <!-- when space or delimiter are found in the fields. It can be set to -->
- <!-- enable or disable. By default, it is set to disable -->
- <QuoteFields>disable</QuoteFields>
- <!-- This is an optional flag to control if the fields need to be escaped -->
- <!-- when unsafe characters are found in the fields. It can be set to -->
- <!-- enable or disable. By default, it is set to enable -->
- <!-- Based on rfc1738, unsafe characters are space, <, >, ", #, %, {, }, |, -->
- <!-- ^, ~, [, ], ` -->
- <EscapeFields>enable</EscapeFields>
- </Access>
- <Diagnostic>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs/ in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named admin.01.log, -->
- <!-- admin.02.log, admin.03.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- admin.00.log will be renamed to admin.01.log and admin.01.log -->
- <!-- will be renamed to admin.02.log and so on until it reach the -->
- <!-- maximum history. Therefore, log file with the highest version -->
- <!-- number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- <core>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- </core>
- <edge>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- </edge>
- <master>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- </master>
- <admin>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- </admin>
- </Diagnostic>
- <Application>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs/ in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named -->
- <!-- application.01.log, application.02.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- application.00.log will be renamed to application.01.log and -->
- <!-- application.01.log will be renamed to application.02.log and -->
- <!-- so on until it reach the maximum history. Therefore, log file with -->
- <!-- the highest version number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- </Application>
- <AuthEvent>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- AuthEvent log file name, everything inside the square brackets will be -->
- <!-- substituted. -->
- <!-- Y represents Year, only YYYY is allowed -->
- <!-- M represents Month, only M or MM are allowed -->
- <!-- D represents Day, only D or DD are allowed -->
- <!-- N represents Version, there is no limit on number of N -->
- <!-- The number of each letter represents number of digits, for example -->
- <!-- April in M is 4 and in MM is 04 -->
- <FileName>authEvent.[NN].log</FileName>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named authEvent.01.log, -->
- <!-- authEvent.02.log, authEvent.03.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- authEvent.00.log will be renamed to authEvent.01.log and -->
- <!-- authEvent.01.log will be renamed to authEvent.02.log and so on until -->
- <!-- it reach the maximum history. Therefore, log file with the highest -->
- <!-- version number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- <!-- The following describes which events to be logged. The various events -->
- <!-- are as follows, -->
- <!-- Event Name Category -->
- <!-- ========== ======== -->
- <!-- 1. connect session -->
- <!-- 2. disconnect session -->
- <!-- 3. publish stream -->
- <!-- 4. unpublish stream -->
- <!-- 5. play stream -->
- <!-- 6. pause stream -->
- <!-- 7. seek stream -->
- <!-- 8. stop stream -->
- <!-- 9. filenametransform stream -->
- <!-- 10. loadsegment stream -->
- <!-- 11. app-start application -->
- <!-- 12. app-stop application -->
- <!-- 13. action authorization -->
- <!-- The desired events are specified as a semi-colon separated list. -->
- <!-- Specifying * will log all events. -->
- <Events>app-start;connect;disconnect;play;pause;stop;filenametransform</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. x-eid Event id -->
- <!-- 4. date Date at which the event occurred -->
- <!-- 5. time Time at which the event occurred -->
- <!-- 6. tz Time zone information -->
- <!-- 7. x-ctx event dependant context information -->
- <!-- 8. x-pid event id -->
- <!-- 9. x-adaptor dll adaptor name -->
- <!-- 10. x-vhost vhost name -->
- <!-- 11. x-app application name -->
- <!-- 12. x-appinst application instance name -->
- <!-- 13. c-ip client ip address -->
- <!-- 14. c-proto connection protocol - rtmp or rtmpt -->
- <!-- 15. s-uri uri of the fms application -->
- <!-- 16. c-referrer uri of the referrer -->
- <!-- 17. c-user-agent user agent -->
- <!-- 18. c-client-id client id -->
- <!-- 19. cs-bytes bytes transferred from client to server -->
- <!-- 20. sc-bytes bytes transferred from server to client -->
- <!-- 21. x-sname stream name -->
- <!-- 22. x-file-size stream size in bytes -->
- <!-- 23. x-file-length stream length in seconds -->
- <!-- 24. x-spos stream position -->
- <!-- 25. cs-stream-bytes stream reset param -->
- <!-- 26. sc-stream-bytes stream ignore param -->
- <!-- 27. s-ip ip address[es] of the server -->
- <!-- 28. x-duration duration of an event/session -->
- <!-- 29. x-status status code -->
- <!-- 30. cs-uri-stem stem of s-uri -->
- <!-- 31. cs-uri-query query portion of s-uri -->
- <!-- 32. x-sname-query query portion of stream uri -->
- <!-- 33. x-file-name Fux-pidll file path of recorded stream -->
- <!-- 34. x-file-ext stream type (flv or mp3) -->
- <!-- 35. c-connect-type type of connection received by the server -->
- <!-- 36. x-service-name name of the service providing the connection -->
- <!-- 37. x-comment Comments -->
- <!-- 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-app;x-appinst;c-ip;x-pid;x-status;x-adaptor;x-sname;x-file-length;x-spos;cs-stream-bytes;
- sc-stream-bytes;x-file-name;x-file-ext;x-file-size</Fields>
- <!-- Delimiter is used to separate between fields -->
- <!-- Recommended: tab or ' '. If no delimiter is specified, default is tab -->
- <!-- Not Recommended: '#', because it is used as comment tag in W3C format -->
- <!-- Disallowed: ''', '"', '.', ':', '-', '\' and all alpha-numeric -->
- <!-- (a-z, A-Z, 0-9). Character ':' and '-' are not allowed because ':' is -->
- <!-- used in the time field and '-' is used in the date field and fields -->
- <!-- with empty value. -->
- <Delimiter></Delimiter>
- <!-- This is an optional flag to control if the fields need to be quoted -->
- <!-- when space or delimiter are found in the fields. It can be set to -->
- <!-- enable or disable. By default, it is set to disable -->
- <QuoteFields>disable</QuoteFields>
- <!-- This is an optional flag to control if the fields need to be escaped -->
- <!-- when unsafe characters are found in the fields. It can be set to -->
- <!-- enable or disable. By default, it is set to enable -->
- <!-- Based on rfc1738, unsafe characters are space, <, >, ", #, %, {, }, |, -->
- <!-- ^, ~, [, ], ` -->
- <EscapeFields>enable</EscapeFields>
- </AuthEvent>
- <AuthMessage>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named -->
- <!-- authMessage.01.log, authMessage.02.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- authMessage.00.log will be renamed to authMessage.01.log and -->
- <!-- authMessage.01.log will be renamed to authMessage.02.log and -->
- <!-- so on until it reach the maximum history. Therefore, log file with -->
- <!-- the highest version number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- </AuthMessage>
- <FileIO>
- <!-- This section configures the server to send log msgs to a -->
- <!-- remote logging server. To enable this feature, set the -->
- <!-- "enable" attribute to true. You can choose the type of -->
- <!-- connection to use by specifying the "type" attribute which -->
- <!-- can be set to either "udp" or "tcp". Default is udp. -->
- <LogServer enable="false" type="udp">
- <!-- Specify the IP and port of the server to log to. -->
- <!-- For example, -->
- <!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort> -->
- <HostPort></HostPort>
- <!-- This is an identifier used to identify the server that -->
- <!-- the log came from. By default, this is the IP address -->
- <!-- of this server. -->
- <ServerID></ServerID>
- <!-- This specifies how many lines to log before including -->
- <!-- the fields header again. -->
- <DisplayFieldsHeader>100</DisplayFieldsHeader>
- </LogServer>
- <!-- Directory in which log files will be placed, by default they are -->
- <!-- placed in logs in the server installation directory. -->
- <Directory>${LOGGER.LOGDIR}</Directory>
- <!-- The time field in a log file can be either in utc or local time. The -->
- <!-- setting here can be used to override the server-wide configuration, -->
- <!-- see <Logging> in Server.xml. -->
- <Time></Time>
- <Rotation>
- <!-- Maximum file size in kilobytes (1024 bytes) -->
- <MaxSize>10240</MaxSize>
- <!-- Rotation Time, there are 2 types -->
- <!-- If type="daily", rotation only occurs every 24 hours, and the format -->
- <!-- is hh:mm, for example 00:00 will rotates every midnight -->
- <!-- If type="duration", rotation occurs when the duration of the log -->
- <!-- exceed a certain length, duration takes a number in minutes -->
- <Schedule type="daily">00:00</Schedule>
- <!-- Max number of log files to keep, files will be named -->
- <!-- fileMessage.01.log, fileMessage.02.log etc. -->
- <History>5</History>
- <!-- When it is time to rotate the log files and Rename is set to true, -->
- <!-- fileMessage.00.log will be renamed to fileMessage.01.log and -->
- <!-- fileMessage.01.log will be renamed to fileMessage.02.log and -->
- <!-- so on until it reach the maximum history. Therefore, log file with -->
- <!-- the highest version number keeps the oldest log history. -->
- <!-- If Rename is set to false, a new log file will be created with the -->
- <!-- next available version when rotation occurs. Therefore, log file -->
- <!-- with the lowest version number keeps the oldest log history. -->
- <!-- Default is true. -->
- <Rename>true</Rename>
- </Rotation>
- </FileIO>
- </Logger>
Advertisement
Add Comment
Please, Sign In to add comment