You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Jay Tomolek (JIRA)" <ji...@apache.org> on 2014/04/27 20:43:15 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 ]
Jay Tomolek updated TS-698:
---------------------------
Attachment: logfilterip.patch
patch file to enable LogFilterIP
> 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
> Fix For: sometime
>
> 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)