每次看access log都会记不住pattern里的各个标识代表的什么意思,记录下,备忘!

tomcat的access log是由实现了org.apache.catalina.AccessLog接口的Valve完成的,(Valve是tomcat配置文件server.xml中的一个标签元素)

下面来简单介绍下tomcat的Access Log Valve

简介

标签属性

访问日志Valve支持一下属性配置

属性 原文描述 瞎比翻译
className Java class name of the implementation to use. This MUST be set to org.apache.catalina.valves.AccessLogValve to use the default access log valve. 指定需要的
directory Absolute or relative pathname of a directory in which log files created by this valve will be placed. If a relative path is specified, it is interpreted as relative to $CATALINA_BASE. If no directory attribute is specified, the default value is "logs" (relative to $CATALINA_BASE).  日志文件存放路径( $CATALINA_BASE的相对路径)
prefix The prefix added to the start of each log file's name. If not specified, the default value is "access_log.".  日志文件统一前缀
suffix The suffix added to the end of each log file's name. If not specified, the default value is "" (a zero-length string), meaning that no suffix will be added.  日志文件统一后缀
fileDateFormat Allows a customized timestamp in the access log file name. The file is rotated whenever the formatted timestamp changes. The default value is yyyy-MM-dd. If you wish to rotate every hour, then set this value to yyyy-MM-dd.HH. The date format will always be localized using the locale en_US.  日志文件名上的时间格式
rotatable Flag to determine if log rotation should occur. If set to false, then this file is never rotated and fileDateFormat is ignored. Default value: true  是否分隔日志文件
renameOnRotate By default for a rotatable log the active access log file name will contain the current timestamp in fileDateFormat. During rotation the file is closed and a new file with the next timestamp in the name is created and used. When setting renameOnRotate to true, the timestamp is no longer part of the active log file name. Only during rotation the file is closed and then renamed to include the timestamp. This is similar to the behavior of most log frameworks when doing time based rotation. Default value: false  当前写入的日志文件不带时间标识
pattern A formatting layout identifying the various information fields from the request and response to be logged, or the word common or combined to select a standard format. See below for more information on configuring this attribute.  
encoding Character set used to write the log file. An empty string means to use the system default character set. Default value: use the system default character set.  编码
locale The locale used to format timestamps in the access log lines. Any timestamps configured using an explicit SimpleDateFormat pattern (%{xxx}t) are formatted in this locale. By default the default locale of the Java process is used. Switching the locale after the AccessLogValve is initialized is not supported. Any timestamps using the common log format (CLF) are always formatted in the locale en_US.  
requestAttributesEnabled Set to true to check for the existence of request attributes (typically set by the RemoteIpValve and similar) that should be used to override the values returned by the request for remote address, remote host, server port and protocol. If the attributes are not set, or this attribute is set to false then the values from the request will be used. If not set, the default value of false will be used.  
conditionIf Turns on conditional logging. If set, requests will be logged only if ServletRequest.getAttribute() is not null. For example, if this value is set to important, then a particular request will only be logged if ServletRequest.getAttribute("important") != null. The use of Filters is an easy way to set/unset the attribute in the ServletRequest on many different requests.  
conditionUnless Turns on conditional logging. If set, requests will be logged only if ServletRequest.getAttribute() is null. For example, if this value is set to junk, then a particular request will only be logged if ServletRequest.getAttribute("junk") == null. The use of Filters is an easy way to set/unset the attribute in the ServletRequest on many different requests.  
condition The same as conditionUnless. This attribute is provided for backwards compatibility.  
buffered Flag to determine if logging will be buffered. If set to false, then access logging will be written after each request. Default value: true  
resolveHosts

This attribute is no longer supported. Use the connector attribute enableLookups instead.

If you have enableLookups on the connector set to true and want to ignore it, use %a instead of %h in the value of pattern.

 

pattern属性

当前请求的request和response中的属性输出

标签 原文解析 瞎比翻译
%a Remote IP address 远程ip地址
%A Local IP address 本地ip地址
%b Bytes sent, excluding HTTP headers, or '-' if zero 不包含http头部的发送字节数
%B Bytes sent, excluding HTTP headers 包含http头部的发送字节数
%h Remote host name (or IP address if enableLookups for the connector is false) 远程主机名(如果标签enableLookups=false,就是ip地址了)
%H Request protocol 使用的协议
%l Remote logical username from identd (always returns '-') 总是返回‘-’,有毛用啊
%m Request method (GET, POST, etc.) 请求方法
%p Local port on which this request was received. See also %{xxx}p below. 接受这次请求的本地端口号
%q Query string (prepended with a '?' if it exists) url后面的查询字符串
%r First line of the request (method and request URI) http请求的第一行?
%s HTTP status code of the response http响应的状态码
%S User session ID 会话id
%t Date and time, in Common Log Format 请求访问时间
%u Remote user that was authenticated (if any), else '-'
%U Requested URL path 请求的路径
%v Local server name 本地服务名
%D Time taken to process the request, in millis 毫秒单位的请求耗时
%T Time taken to process the request, in seconds 秒单位的请求耗时
%F Time taken to commit the response, in millis 毫秒单位的提交响应结果的耗时
%I Current request thread name (can compare later with stacktraces) 当前请求的线程名称

请求头部、响应头部、cookies、session及特殊时间戳的信息输出

标识 原文解析 瞎比翻译
%{xxx}i write value of incoming header with name xxx 请求头部属性 
%{xxx}o write value of outgoing header with name xxx  响应头部属性
%{xxx}c write value of cookie with name xxx  cookie信息
%{xxx}r write value of ServletRequest attribute with name xxx  request?和上面的一样功能?
%{xxx}s write value of HttpSession attribute with name xxx  会话信息
%{xxx}p write local (server) port (xxx==local) or remote (client) port (xxx=remote)  端口
%{xxx}t write timestamp at the end of the request formatted using the enhanced SimpleDateFormat pattern xxx  时间戳

参考

http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html

tomcat access日志的更多相关文章

  1. 完整的多项匹配tomcat access日志的正则

    <pre name="code" class="html"><pre name="code" class="ht ...

  2. Servlet、Tomcat访问(access)日志配置、记录Post请求参数

    一.运行环境: Maven:3.5.2(点击下载) ,下载页 Tomcat:8.5.29(点击下载) ,下载页 JDK:jdk1.7.0_80(点击下载) ,下载页 MavenDependency: ...

  3. Tomcat访问(access)日志配置

    在tomcat的access中打印出请求的情况可以帮助我们分析问题,通常比较关注的有访问IP.线程号.访问url.返回状态码.访问时间.持续时间. 最近在跟一个图片请求超时的问题,需要在项目的acce ...

  4. spring boot打开tomcat的access日志

    spring boot虽说内置了tomcat,但打出来的是jar包而非war包,更没有access日志,那么如何打开access日志呢?只需在application.properties中加入相关配置 ...

  5. Tomcat访问日志详细配置

    在server.xml里的<host>标签下加上 <Valve className="org.apache.catalina.valves.AccessLogValve&q ...

  6. tomcat详细日志配置

    在server.xml里的<host>标签下加上<Valve className="org.apache.catalina.valves.AccessLogValve&qu ...

  7. Tomcat access log配置

    在tomcat的access中打印出请求的情况可以帮助我们分析问题,通常比较关注的有访问IP.线程号.访问url.返回状态码.访问时间.持续时间. 在Spring boot中使用了内嵌的tomcat, ...

  8. spring boot(13)-logback和access日志

    logback logback出自log4j的作者,性能和功能相比log4j作出了一些改进,而配置方法和log4j类似,是spring boot的默认日志组件.在application.propert ...

  9. Tomcat中日志组件

    Tomcat日志组件 AccessLog接口 public interface AccessLog { public void log(Request request, Response respon ...

随机推荐

  1. MS17-010远程溢出漏洞 - 永恒之蓝 [CVE-2017-0143]

    MS17-010远程溢出漏洞(永恒之蓝) Ti:2019-12-25 By:Mirror王宇阳 MS17-010 CVE-2017-0143 MS17-010 CVE-2017-0144 MS17-0 ...

  2. Python判断文件和文件夹是否存在的方法

    Python判断文件和文件夹是否存在的方法 这篇文章主要介绍了Python判断文件和文件夹是否存在的方法,本文还讲解了判断是否为文件或者目录的方法.os.path.lexist的作用.FTP中判断文件 ...

  3. pymysql.err.OperationalError: (2013, 'Lost connection to MySQL server during query')

    pymysql错误: pymysql.err.OperationalError: (2013, 'Lost connection to MySQL server during query') pymy ...

  4. spark-ML之朴素贝叶斯

    训练语料格式 自定义五个类别及其标签:0 运费.1 寄件.2 人工.3 改单.4 催单.5 其他业务类. 从原数据中挑选一部分作为训练语料和测试语料  建立模型测试并保存 import org.apa ...

  5. LeetCode169 Majority Element, LintCode47 Majority Number II, LeetCode229 Majority Element II, LintCode48 Majority Number III

    LeetCode169. Majority Element Given an array of size n, find the majority element. The majority elem ...

  6. QPS 提升60%,揭秘阿里巴巴轻量级开源 Web 服务器 Tengine 负载均衡算法

    前言 在阿里七层流量入口接入层(Application Gateway)场景下, Nginx 官方的Smooth Weighted Round-Robin( SWRR )负载均衡算法已经无法再完美施展 ...

  7. windows和linux下读取文件乱码的终极解决办法!

    乱码是个很恶心的问题. windows和linux读取txt文件,一旦读取了,编码发生改变,就无法再还原了,只有重启项目. 网上有很多方法都是读取文件头,方法很好,但是亲测都不能用(右移8位判断0xf ...

  8. python的sorted排序具体解释

    排序.在编程中常常遇到的算法.我也在几篇文章中介绍了一些关于排序的算法. 有的高级语言内置了一些排序函数.本文讲述Python在这方面的工作.供使用python的程序猿们參考,也让没有使用python ...

  9. sql函数的使用——转换函数

    转换函数用于将数据类型从一种转为另外一种,在某些情况下,oracle server允许值的数据类型和实际的不一样,这时oracle server会隐含的转化数据类型,比如: create table ...

  10. Java练习 SDUT-2561_九九乘法表

    九九乘法表 Time Limit: 1000 ms Memory Limit: 65536 KiB Problem Description 九九乘法表是数学学习的基础,今天我们就来看看乘法表的相关问题 ...