access-log

Understanding Apache's access log

由 こ雲淡風輕ζ 提交于 2019-12-17 08:05:09
问题 What do each of the things in this line from my access log mean? 127.0.0.1 - - [05/Feb/2012:17:11:55 +0000] "GET / HTTP/1.1" 200 140 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.5 Safari/535.19" 回答1: You seem to be using the combined log format. LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined %h is the remote host (ie the client IP) %l is the identity of the user determined by identd (not usually used since

Aggregating a list of http log paths in kibana

由 谁说我不能喝 提交于 2019-12-12 04:30:56
问题 I have a nginx->fluentd->elasticsearch->kibana stack up and running. Trying to figure if I can do something like a "terms" panel but with a path string component from logs. Using a terms panel directly on that results in top used words from paths, e.g. for drupal it shows "node" as the most popular, which is quite useless without actual node id. Is that something that is possible to do with elasticsearch? Update : Here's a sample of my logs: "path": "/node/123" "path": "/node/456" "path": "

Log in value from Set-Cookie header in nginx

由 喜夏-厌秋 提交于 2019-12-05 22:37:05
Is it possible to write in nginx access log value of key 'uuid' from Cookie for server response (header: Set-Cookie)? $cookie_uuid - return uuid that sent client $sent_http_set_cookie - return whole header Set-Cookie: 'uuid=897587e7-a733-422f-9daa-b3105a5895aa; domain=domain.com; path=/; expires=Tue, 09-Aug-2033 01:17:54 GMT', but I need save only value for key 'uuid' Thanks map $sent_http_set_cookie $resp_uuid { ~*uuid=(?<u>[0-9a-f-]+) $u; } Reference: http://nginx.org/r/map man pcresyntax 来源： https://stackoverflow.com/questions/18138503/log-in-value-from-set-cookie-header-in-nginx

How to not log a get request parameter in the nginx access logs?

由 断了今生、忘了曾经 提交于 2019-12-04 10:40:25
问题 I require access logs enabled, but for compliance reasons, cannot log a sensitive GET request parameter's data in the access logs. While I know, I could parse the logs (after-the-fact) and sanitize them, this is not an acceptable solution -- because for compliance reasons logs can't be tampered with. http://www.example.com/resource?param1=123&sensitive_param=sensitive_data How can I prevent the "sensitive_data" parameter value from being written to the logs? Here were some ideas: Send in POST

How to not log a get request parameter in the nginx access logs?

由 谁说胖子不能爱 提交于 2019-12-03 06:21:08
I require access logs enabled, but for compliance reasons, cannot log a sensitive GET request parameter's data in the access logs. While I know, I could parse the logs (after-the-fact) and sanitize them, this is not an acceptable solution -- because for compliance reasons logs can't be tampered with. http://www.example.com/resource?param1=123&sensitive_param=sensitive_data How can I prevent the "sensitive_data" parameter value from being written to the logs? Here were some ideas: Send in POST request -- is not an option with JSONP. Use a new location rule for "resource" and set an access log

Understanding Apache's access log

由 无人久伴 提交于 2019-11-27 05:57:32
What do each of the things in this line from my access log mean? 127.0.0.1 - - [05/Feb/2012:17:11:55 +0000] "GET / HTTP/1.1" 200 140 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.5 Safari/535.19" Joachim Isaksson You seem to be using the combined log format . LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" combined %h is the remote host (ie the client IP) %l is the identity of the user determined by identd (not usually used since not reliable) %u is the user name determined by HTTP authentication %t is the time the
订阅 access-log