trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jpe...@apache.org
Subject [trafficserver] 05/05: doc: Remove logs_xml.config documentation.
Date Tue, 27 Sep 2016 17:12:17 GMT
This is an automated email from the ASF dual-hosted git repository.

jpeach pushed a commit to branch master
in repository https://git-dual.apache.org/repos/asf/trafficserver.git

commit 9f1453a70883ea921d458a2b7909ec181f64e59f
Author: James Peach <jpeach@apache.org>
AuthorDate: Tue Sep 27 10:07:54 2016 -0700

    doc: Remove logs_xml.config documentation.
---
 doc/admin-guide/files/logs_xml.config.en.rst       |  28 -
 .../admin-guide/files/logs_xml.config.en.po        | 575 ---------------------
 2 files changed, 603 deletions(-)

diff --git a/doc/admin-guide/files/logs_xml.config.en.rst b/doc/admin-guide/files/logs_xml.config.en.rst
deleted file mode 100644
index eff43ae..0000000
--- a/doc/admin-guide/files/logs_xml.config.en.rst
+++ /dev/null
@@ -1,28 +0,0 @@
-.. Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-   http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.
-
-.. include:: ../../common.defs
-
-logs_xml.config
-***************
-
-.. important::
-
-   This configuration file has been replaced with :file:`logging.config`.
-   Please refer to the documentation on that file for managing your custom
-   log formats and filters.
-
diff --git a/doc/locale/ja/LC_MESSAGES/admin-guide/files/logs_xml.config.en.po b/doc/locale/ja/LC_MESSAGES/admin-guide/files/logs_xml.config.en.po
deleted file mode 100644
index 9ce0a9e..0000000
--- a/doc/locale/ja/LC_MESSAGES/admin-guide/files/logs_xml.config.en.po
+++ /dev/null
@@ -1,575 +0,0 @@
-# SOME DESCRIPTIVE TITLE.
-# Copyright (C) 2015, dev@trafficserver.apache.org
-# This file is distributed under the same license as the Apache Traffic
-# Server package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, 2016.
-#
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: Apache Traffic Server 6.2\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2016-02-14 12:15+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@li.org>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"Generated-By: Babel 2.2.0\n"
-
-#: ../../../admin-guide/files/logging.config.en.rst:20
-msgid "logging.config"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:24
-msgid ""
-"The :file:`logging.config` file defines the custom log file formats, "
-"filters, and processing options. The format of this file is modeled after "
-"XML, the Extensible Markup Language."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:29
-msgid "Format"
-msgstr "フォーマット"
-
-#: ../../../admin-guide/files/logging.config.en.rst:31
-msgid "The :file:`logging.config` file contains the specifications below:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:33
-msgid ""
-"``LogFormat`` specifies the fields to be gathered from each protocol event "
-"access."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:35
-msgid ""
-"``LogFilter`` specifies the filters that are used to include or exclude "
-"certain entries being logged based on the value of a field within that "
-"entry."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:38
-msgid ""
-"``LogObject`` specifies an object that contains a particular format, a "
-"local filename, filters, and collation servers."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:41
-msgid ""
-"The :file:`logging.config` file ignores extra white space, blank lines, "
-"and all comments."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:47
-msgid "LogFormat"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:49
-msgid "The following list shows ``LogFormat`` specifications."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:57
-msgid "``<Name = \"valid_format_name\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:54
-msgid ""
-"Required Valid format names include any name except ``squid``, ``common``, "
-"``extended``, or ``extended2``, which are pre-defined formats. There is no "
-"default for this tag. The format object needs to be above the the LogObject "
-"object."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:86
-msgid "``<Format = \"valid_format_specification\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:62
-msgid ""
-"Required A valid format specification is a printf-style string describing "
-"each log entry when formatted for ASCII output."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:66
-msgid "The printf-style could accept Oct/Hex escape representation:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:68
-msgid ""
-"``\\abc`` is Oct escape sequence, a,b,c should be one of [0-9], and (a*8^2 "
-"+ b*8 + c) should be greater than 0 and less than 255."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:70
-msgid ""
-"``\\xab`` is Hex escape sequence, a,b should be one of [0-9, a-f, A-F], and "
-"(a*16 + b) should be greater than 0 and less than 255."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:73
-msgid ""
-"Use ``%<`` ``field`` ``>`` as a placeholder for valid field names. For more "
-"information, refer to :ref:`custom-logging-fields`."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:76
-msgid "The specified field can be one of the following types:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:78
-msgid ""
-"Simple. For example: ``%<cqu>`` A field within a container, such as an HTTP "
-"header or a statistic. Fields of this type have the syntax: ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:84
-msgid ""
-"Aggregates, such as ``COUNT``, ``SUM``, ``AVG``, ``FIRST``, ``LAST``. "
-"Fields of this type have the syntax: ``%<operator (`` ``field`` ``)>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:90
-msgid ""
-"You cannot create a format specification that contains both aggregate "
-"operators and regular fields."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:104
-msgid "``<Interval = \"aggregate_interval_secs\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:93
-msgid ""
-"Optional Use this tag when the format contains aggregate operators. The "
-"value \"``aggregate_interval_secs``\\\" represents the number of seconds "
-"between individual aggregate values being produced."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:98
-msgid "The valid set of aggregate operators are:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:100
-msgid "COUNT"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:101
-msgid "SUM"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:102
-msgid "AVG"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:103
-msgid "FIRST"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:104
-msgid "LAST"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:109
-msgid "LogFilter"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:111
-msgid "The following list shows the ``LogFilter`` specifications."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:115
-msgid "``<Name = \"valid_filter_name\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:114
-msgid "Required All filters must be uniquely named."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:143
-msgid ""
-"``<Condition = \"valid_log_field valid_operator valid_comparison_value\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:118
-msgid "Required This field contains the following elements:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:121
-msgid ""
-"``valid_log_field`` - the field that will be compared against the given "
-"value. For more information, refer to :ref:`logging-format-cross-reference`."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:124
-msgid ""
-"``valid_operator_field`` - any one of the following: ``MATCH``, "
-"``CASE_INSENSITIVE_MATCH``, ``CONTAIN``, ``CASE_INSENSITIVE_CONTAIN``."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:128
-msgid ""
-"``MATCH`` is true if the field and value are identical (case-sensitive)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:130
-msgid ""
-"``CASE_INSENSITIVE_MATCH`` is similar to ``MATCH``, except that it is case-"
-"insensitive."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:132
-msgid ""
-"``CONTAIN`` is true if the field contains the value (the value is a "
-"substring of the field)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:134
-msgid ""
-"``CASE_INSENSITIVE_CONTAIN`` is a case-insensitive version of ``CONTAIN``."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:137
-msgid ""
-"``valid_comparison_value`` - any string or integer matching the field type. "
-"For integer values, all of the operators are equivalent and mean that the "
-"field must be equal to the specified value."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:141
-msgid ""
-"For IP address fields, this can be a list of IP addresses and include "
-"ranges. A range is an IP address, followed by a dash '``-``', and then "
-"another IP address of the same family. For instance, the 10/8 network can "
-"be represented by ``10.0.0.0-10.255.255.255``. Currently network specifiers "
-"are not supported."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:147
-msgid ""
-"There are no negative comparison operators. If you want to specify a "
-"negative condition, then use the ``Action`` field to ``REJECT`` the record."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:155
-msgid "``<Action = \"valid_action_field\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:152
-msgid ""
-"Required: ``ACCEPT`` or ``REJECT`` or ``WIPE_FIELD_VALUE``. ACCEPT or "
-"REJECT instructs Traffic Server to either accept or reject records that "
-"satisfy the filter condition. WIPE_FIELD_VALUE wipes out the values of the "
-"query params in the url fields specified in the Condition."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:160
-msgid ""
-"NOTES: 1. WIPE_FIELD_VALUE action is only applied to the parameters in the "
-"query part."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:158
-msgid "Multiple parameters can be listed in a single WIPE_FIELD_VALUE filter"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:159
-msgid ""
-"If the same parameter appears more than once in the query part , only the "
-"value of the first occurance is wiped"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:165
-msgid "LogObject"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:167
-msgid "The following list shows the ``LogObject`` specifications."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:174
-msgid "``<Format = \"valid_format_name\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:170
-msgid ""
-"Required Valid format names include the predefined logging formats: "
-"``squid``, ``common``, ``extended``, and ``extended2``, as well as any "
-"previously-defined custom log formats. There is no default for this tag. "
-"The format object needs to be above the the LogObject object."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:189
-msgid "``<Filename = \"file_name\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:177
-msgid ""
-"Required The filename to which the given log file is written on the local "
-"file system or on a remote collation server. No local log file will be "
-"created if you fail to specify this tag. All filenames are relative to the "
-"default logging directory."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:183
-msgid ""
-"If the name does not contain an extension (for example, ``squid``), then "
-"the extension ``.log`` is automatically appended to it for ASCII logs and "
-"``.blog`` for binary logs (refer to :ref:`Mode = \"valid_logging_mode\" "
-"<LogObject-Mode>`)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:188
-msgid ""
-"If you do not want an extension to be added, then end the filename with a "
-"single (.) dot (for example: ``squid.`` )."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:217
-msgid "``<Mode = \"valid_logging_mode\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:194
-msgid ""
-"Optional Valid logging modes include ``ascii`` , ``binary`` , and "
-"``ascii_pipe`` . The default is ``ascii`` ."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:198
-msgid ""
-"Use ``ascii`` to create event log files in human-readable form (plain "
-"ASCII)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:200
-msgid ""
-"Use ``binary`` to create event log files in binary format. Binary log files "
-"generate lower system overhead and occupy less space on the disk (depending "
-"on the information being logged). You must use the :program:"
-"`traffic_logcat` utility to translate binary log files to ASCII format "
-"before you can read them."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:205
-msgid ""
-"Use ``ascii_pipe`` to write log entries to a UNIX named pipe (a buffer in "
-"memory). Other processes can then read the data using standard I/O "
-"functions. The advantage of using this option is that Traffic Server does "
-"not have to write to disk, which frees disk space and bandwidth for other "
-"tasks. In addition, writing to a pipe does not stop when logging space is "
-"exhausted because the pipe does not use disk space."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:213
-msgid ""
-"If you are using a collation server, then the log is written to a pipe on "
-"the collation server. A local pipe is created even before a transaction is "
-"processed, so you can see the pipe right after Traffic Server starts. Pipes "
-"on a collation server, however, *are* created when Traffic Server starts."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:224
-msgid "``<Filters = \"list_of_valid_filter_names\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:220
-msgid ""
-"Optional A comma-separated list of names of any previously-defined log "
-"filters. If more than one filter is specified, then all filters must accept "
-"a record for the record to be logged. The filters need to be above the "
-"LogObject object."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:230
-msgid "``<Protocols = \"list_of_valid_protocols\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:227
-msgid ""
-"Optional A comma-separated list of the protocols this object should log. "
-"Valid protocol names for this release are ``HTTP`` (FTP is deprecated)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:235
-msgid "``<ServerHosts = \"list_of_valid_servers\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:233
-msgid ""
-"Optional A comma-separated list of valid hostnames.This tag indicates that "
-"only entries from the named servers will be included in the file."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:250
-msgid ""
-"``<CollationHosts = \"list_of_valid_hostnames:port|failover hosts\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:240
-msgid ""
-"Optional A comma-separated list of collation servers (with pipe delimited "
-"failover servers) to which all log entries (for this object) are forwarded. "
-"Collation servers can be specified by name or IP address. Specify the "
-"collation port with a colon after the name. For example, in ``host1:5000|"
-"failhostA:5000|failhostB:6000, host2:6000`` logs would be sent to host1 and "
-"host2, with failhostA and failhostB acting as failover hosts for host1. "
-"When host1 disconnects, logs would be sent to failhostA. If failhostA "
-"disconnects, log entries would be sent to failhostB until host1 or "
-"failhostA comes back. Logs would also be sent to host2."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:256
-msgid "``<Header = \"header\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:253
-msgid ""
-"Optional The header text you want the log files to contain. The header text "
-"appears at the beginning of the log file, just before the first record."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:276
-msgid "``<RollingEnabled = \"truth value\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:259
-msgid ""
-"Optional Enables or disables log file rolling for the ``LogObject``. This "
-"setting overrides the value for the :ts:cv:`proxy.config.log."
-"rolling_enabled` variable in the :file:`records.config` file. Set *truth "
-"value* to one of the following values:"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:266
-msgid "``0`` to disable rolling for this particular ``LogObject``."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:267
-msgid ""
-"``1`` to roll log files at specific intervals during the day (you specify "
-"time intervals with the ``RollingIntervalSec`` and ``RollingOffsetHr`` "
-"fields)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:270
-msgid ""
-"``2`` to roll log files when they reach a certain size (you specify the "
-"size with the ``RollingSizeMb`` field)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:272
-msgid ""
-"``3`` to roll log files at specific intervals during the day or when they "
-"reach a certain size (whichever occurs first)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:274
-msgid ""
-"``4`` to roll log files at specific intervals during the day when log files "
-"reach a specific size (at a specified time if the file is of the specified "
-"size)."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:288
-msgid "``<RollingIntervalSec = \"seconds\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:281
-msgid ""
-"Optional The seconds between log file rolling for the ``LogObject``; "
-"enables you to specify different rolling intervals for different "
-"``LogObjects``."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:286
-msgid ""
-"This setting overrides the value for :ts:cv:`proxy.config.log."
-"rolling_interval_sec` in the :file:`records.config` file."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:298
-msgid "``<RollingOffsetHr = \"hour\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:291
-msgid ""
-"Optional Specifies an hour (from 0 to 23) at which rolling is guaranteed to "
-"align. Rolling might start before then, but a rolled file will be produced "
-"only at that time. The impact of this setting is only noticeable if the "
-"rolling interval is larger than one hour. This setting overrides the "
-"configuration setting for :ts:cv:`proxy.config.log.rolling_offset_hr` in "
-"the :file:`records.config` file."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:302
-msgid "``<RollingSizeMb = \"size_in_MB\"/>``"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:301
-msgid "Optional The size at which log files are rolled."
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:305
-msgid "Examples"
-msgstr "例"
-
-#: ../../../admin-guide/files/logging.config.en.rst:307
-msgid ""
-"The following is an example of a ``LogFormat`` specification that collects "
-"information using three common fields: ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:315
-msgid ""
-"The following is an example of a ``LogFormat`` specification that uses "
-"aggregate operators: ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:324
-msgid ""
-"The following is an example of a ``LogFilter`` that will cause only "
-"``REFRESH_HIT`` entries to be logged: ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:335
-msgid ""
-"When specifying the field in the filter condition, you can omit the ``"
-"%<>``. This means that the filter below is equivalent to the example "
-"directly above: ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:345
-msgid ""
-"The following is an example of a ``LogFilter`` that will cause the value of "
-"passwd field be wiped in ``cquc`` ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:354
-msgid ""
-"The following is an example of a ``LogObject`` specification that creates a "
-"local log file for the minimal format defined earlier. The log filename "
-"will be ``minimal.log`` because this is an ASCII log file (the default).::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:364
-msgid ""
-"The following is an example of a ``LogObject`` specification that includes "
-"only HTTP requests served by hosts in the domain ``company.com`` or by the "
-"specific server ``server.somewhere.com``. Log entries are sent to port 4000 "
-"of the collation host ``logs.company.com`` and to port 5000 of the "
-"collation host ``209.131.52.129.`` ::"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:381
-msgid "WELF"
-msgstr ""
-
-#: ../../../admin-guide/files/logging.config.en.rst:383
-msgid ""
-"Traffic Server supports WELF (WebTrends Enhanced Log Format) so you can "
-"analyze Traffic Server log files with WebTrends reporting tools. A "
-"predefined ``<LogFormat>`` that is compatible with WELF is provided in the :"
-"file:`logging.config` file (shown below). To create a WELF format log "
-"file, create a ``<LogObject>`` that uses this predefined format. ::"
-msgstr ""

-- 
To stop receiving notification emails like this one, please contact
"commits@trafficserver.apache.org" <commits@trafficserver.apache.org>.

Mime
View raw message