You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by ml...@apache.org on 2018/01/23 02:16:07 UTC

[trafficserver] branch master updated: Logging can only have 1 accept filter

This is an automated email from the ASF dual-hosted git repository.

mlibbey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/master by this push:
     new 8cbc52d  Logging can only have 1 accept filter
8cbc52d is described below

commit 8cbc52d973741691d3b3c0e3d96a8ee2f1056c8d
Author: Miles Libbey <ml...@apache.org>
AuthorDate: Tue Jan 9 18:52:07 2018 -0800

    Logging can only have 1 accept filter
    
    We support multiple reject filters, but only 1 accept filter. For
    instance
    
    example = filter.accept('%<cquuh> MATCH example.com')
    foo = filter.accept('%<cquuh> MATCH another.example.com')
    log.ascii {
      Filename = 'refreshhit_summary',
      Format = summaryfmt,
      Filters = { example, foo }
    }
    and all variants will not log anything to refreshhit_summary.
    
    However,
    
    example = filter.reject('%<cquuh> MATCH example.com')
    foo = filter.reject('%<cquuh> MATCH another.example.com')
    log.ascii {
      Filename = 'refreshhit_summary',
      Format = summaryfmt,
      Filters = { example, foo }
    }
    will not contain logs from example.com and another.example.com
---
 doc/admin-guide/files/logging.config.en.rst | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/doc/admin-guide/files/logging.config.en.rst b/doc/admin-guide/files/logging.config.en.rst
index 77a5b96..d368435 100644
--- a/doc/admin-guide/files/logging.config.en.rst
+++ b/doc/admin-guide/files/logging.config.en.rst
@@ -168,11 +168,11 @@ Filter objects are created by calling one of the following functions:
 
 filter.accept(string)
     Creates a filter object which accepts events for logging which match the
-    rule specified in ``string``.
+    rule specified in ``string``. Note that you may only have one accept filter.
 
 filter.reject(string)
     Creates a filter object which rejects events for logging which match the
-    rule specified in ``string``.
+    rule specified in ``string``. You may have multiple reject filters.
 
 filter.wipe(string)
     Creates a filter object which clears the values of query parameters listed
@@ -237,10 +237,11 @@ supported at this time.
 
 .. note::
 
-    It may be tempting to attach multiple Filters to a log object to accept or
+    It may be tempting to attach multiple Filters to a log object
     reject multiple log fields (in lieu of providing a single comma separated list
-    to a single Filter). Avoid this temptation and use a comma separated list
-    instead. Attaching multiple filters does the opposite of what you'd
+    to a single Filter). Avoid this temptation and use a comma separated list of reject objects
+    instead. Remember that you may not have multiple accept filter objects.
+    Attaching multiple filters does the opposite of what you'd
     expect. If, for example, we had 2 accept log filters, each disjoint from the other,
     nothing will ever get logged on the given log object.
 
@@ -314,7 +315,8 @@ RollingOffsetHr     number      Specifies an hour (from 0 to 23) at which log
 RollingSizeMb       number      Size, in megabytes, at which log files are
                                 rolled.
 Filters             array of    The optional list of filter objects which
-                    filters     restrict the individual events logged.
+                    filters     restrict the individual events logged. The array
+                                may only contain one accept filter.
 CollationHosts      array of    If present, one or more strings specifying the
                     strings     log collation hosts to which logs should be
                                 delivered, each in the form of "<ip>:<port>".

-- 
To stop receiving notification emails like this one, please contact
mlibbey@apache.org.