[lemma=logformat] [tag="." | □]
[lemma=logformat] [tag="." | □ | □]
[lemma=logformat] [tag="." | !□]
So , the LogFormat line above , from the default httpd.conf file , creates a log format called common , which contains the remote host , remote logname , remote user , the time of the transaction , the first line of the request , the status of the request , and the number of bytes sent . The second form of the LogFormat directive associates an explicit format with a nickname . You will need to give analog two LOGFORMAT commands to tell it about the two different formats . For other web servers , consult the AWStats LogFormat parameter values to get a list of data elements required for complete reporting . The options available for the format are exactly the same as for the argument of the LogFormat directive . The LogFormat directive can be used to simplify the selection of the contents of the logs . Various other contributions include the original Apache 0.6 content negotiation code , the SpareServers machinery ( for better or worse ) , the experimental ( as of 0.8 / 1.0 ) dld module and LogFormat support , and the 0.8 / 1.0 Configuration script . In addition , you must manually map each field being logged using the LogFormat parameter ; otherwise , most of your data file will appear as corrupted to AWStats . Instead , the log format is determined by the most recently specified LogFormat directive that does not define a nickname . It can specify either a nickname defined by a previous LogFormat directive , or it can be an explicit format string as described in the log formats section . If your percentage of corrupted records is high and you have many records , you probably have a mismatch between the fields and their order in your log file , and what you have declared with the AWStats LogFormat parameter .