You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/05/19 17:17:39 UTC

[jira] [Updated] (TS-698) LogFilter should support an actual IP type and matching rules

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

Bryan Call updated TS-698:
--------------------------

    Fix Version/s:     (was: 5.0.0)
                   5.1.0

> LogFilter should support an actual IP type and matching rules
> -------------------------------------------------------------
>
>                 Key: TS-698
>                 URL: https://issues.apache.org/jira/browse/TS-698
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.1.6
>         Environment: N/A
>            Reporter: Eric Connell
>            Assignee: Alan M. Carroll
>            Priority: Minor
>              Labels: review
>             Fix For: 5.1.0
>
>         Attachments: logfilterip.patch
>
>
> The LogFilter configuration in logs_xml.config should support a native IPv4 and IPv6 filtering.  For example, it would be handy to be able to filter out log lines from a specific server or netblock.  For example, the following config would reject log lines for all hosts in the 10/8 network:
> {code}
> <LogFilter>
>     <Name = "local_net"/>
>     <Condition = "chi MATCH 10.0.0.0/8"/>
>     <Action = "REJECT"/>
> </LogFilter> 
>       
> <LogFormat>
>   <Name = "access_log"/>
>   <Format = "%<shi>"/>
> </LogFormat> 
> <LogObject> 
>   <Format = "access_log"/>
>   <Filename = "access_log"/>
>   <Filters = "local_net"/>
> </LogObject> 
> {code} 



--
This message was sent by Atlassian JIRA
(v6.2#6252)