You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2015/06/13 00:50:00 UTC

[jira] [Updated] (MESOS-2519) Log IP addresses from HTTP requests

     [ https://issues.apache.org/jira/browse/MESOS-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Mahler updated MESOS-2519:
-----------------------------------
    Sprint: Twitter Q2 Sprint 2, Twitter Mesos Q2 Sprint 5  (was: Twitter Q2 Sprint 2)

> Log IP addresses from HTTP requests
> -----------------------------------
>
>                 Key: MESOS-2519
>                 URL: https://issues.apache.org/jira/browse/MESOS-2519
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: David Robinson
>            Assignee: Benjamin Mahler
>            Priority: Minor
>              Labels: twitter
>             Fix For: 0.23.0
>
>
> Querying /master/state.json is an expensive operation when a cluster is large, and it's possible to DOS the master via frequent and repeated queries (which is a separate problem). Querying the endpoint results in a log entry being written, but the entry lacks useful information, such as an IP address, response code and response size. These details are useful for tracking down who/what is querying the endpoint. Consider adding these details to the log entry, or even writing a separate [access|https://httpd.apache.org/docs/trunk/logs.html#accesslog] [log|https://httpd.apache.org/docs/trunk/logs.html#common]. Also consider writing log entries for _all_ HTTP requests (/metrics/snapshot produces no log entries).
> {noformat:title=sample log entry}
> I0319 18:06:18.824846 10521 http.cpp:478] HTTP request for '/master/state.json'
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)