This is an automated email from the ASF dual-hosted git repository.
sudheerv pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
commit dd3d50055c75b5247662ce267c943ed40ceaf796
Author: Sudheer Vinukonda <sudhe...@apache.org>
AuthorDate: Mon Jul 15 15:19:58 2019 -0700
Update docs to document wipe_field_action that we use in production
---
doc/admin-guide/files/logging.yaml.en.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/admin-guide/files/logging.yaml.en.rst
b/doc/admin-guide/files/logging.yaml.en.rst
index 96a6fe3..a53d053 100644
--- a/doc/admin-guide/files/logging.yaml.en.rst
+++ b/doc/admin-guide/files/logging.yaml.en.rst
@@ -159,14 +159,14 @@ given one.
Filters
-------
-Two different type of filters are available: ``accept`` and ``reject``. They
-may be used, optionally, to accept or reject logging for matching events.
+Trafficserver supports different type of filters : ``accept``, ``reject`` and
``wipe_field_value``.
+They may be used, optionally, to accept, reject logging or mask query param
values for matching events.
Filter objects are created by assigning them a ``name`` to be used later to
-refer to the filter, as well as an ``action`` (either ``accept`` or
-``reject``). ``Accept`` and ``reject`` filters require a ``condition`` against
-which to match all events. The ``condition`` fields must be in the following
-format::
+refer to the filter, as well as an ``action`` (either ``accept``, ``reject`` or
+``wipe_field_value``). ``Accept``, ``reject`` or ``wipe_field_value` filters
require
+a ``condition`` against which to match all events. The ``condition`` fields
must
+be in the following format::
<field> <operator> <value>
