You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ta...@apache.org on 2019/10/08 18:22:43 UTC
[impala] 01/02: IMPALA-9014: [DOCS] Update impala_logging.xml
This is an automated email from the ASF dual-hosted git repository.
tarmstrong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git
commit 2465bc5c076d1f88b04dc3802647b0f702d87123
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Fri Oct 4 17:09:24 2019 -0700
IMPALA-9014: [DOCS] Update impala_logging.xml
Change-Id: I30867ee197cc5a10efc9947512c186a17bd7f6a8
Reviewed-on: http://gerrit.cloudera.org:8080/14376
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
---
docs/topics/impala_logging.xml | 76 +++++-------------------------------------
1 file changed, 8 insertions(+), 68 deletions(-)
diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml
index da59760..ec87e4a 100644
--- a/docs/topics/impala_logging.xml
+++ b/docs/topics/impala_logging.xml
@@ -153,18 +153,6 @@ under the License.
<codeph>.WARNING</codeph>, and <codeph>.ERROR</codeph> files are physically
represented as symbolic links to the latest applicable log files.
</li>
-
- <li> The init script for the <codeph>impala-server</codeph> service also
- produces a consolidated log file
- <codeph>/var/log/impalad/impala-server.log</codeph>, with all the
- same information as the corresponding<codeph>.INFO</codeph>,
- <codeph>.WARNING</codeph>, and <codeph>.ERROR</codeph> files. </li>
-
- <li> The init script for the <codeph>impala-state-store</codeph> service
- also produces a consolidated log file
- <codeph>/var/log/impalad/impala-state-store.log</codeph>, with all
- the same information as the corresponding<codeph>.INFO</codeph>,
- <codeph>.WARNING</codeph>, and <codeph>.ERROR</codeph> files. </li>
</ul>
<p>
@@ -192,27 +180,6 @@ under the License.
</concept>
- <concept id="logs_managing">
-
- <title>Managing Impala Logs</title>
-
- <prolog>
- <metadata>
- <data name="Category" value="Administrators"/>
- </metadata>
- </prolog>
-
- <conbody>
-
- <p>
- Review Impala log files on each host, when you have traced an issue back to a specific
- system.
- </p>
-
- </conbody>
-
- </concept>
-
<concept id="logs_rotate">
<title>Rotating Impala Logs</title>
@@ -297,12 +264,6 @@ under the License.
<filepath>impalad.ERROR</filepath> files, which contain the subsets of
messages indicating potential problems.) </p>
- <p>
- On a machine named <codeph>impala.example.com</codeph> with default settings, you could
- view the Impala logs on that machine by using a browser to access
- <codeph>http://impala.example.com:25000/logs</codeph>.
- </p>
-
<note>
<p>
The web interface limits the amount of logging information displayed. To view every
@@ -374,26 +335,6 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
</li>
</ul>
- <p>
- There is information about each job Impala has run. Because each Impala job creates an
- additional set of data about queries, the amount of job specific data may be very large.
- Logs may contained detailed information on jobs. These detailed log entries may include:
- </p>
-
- <ul>
- <li>
- The composition of the query.
- </li>
-
- <li>
- The degree of data locality.
- </li>
-
- <li>
- Statistics on data throughput and response times.
- </li>
- </ul>
-
</conbody>
</concept>
@@ -482,15 +423,14 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
<conbody>
<p>
- <indexterm audience="hidden">redaction</indexterm>
- <term>Log redaction</term> is a security feature that prevents sensitive information
- from being displayed in locations used by administrators for monitoring and
- troubleshooting, such as log files and the Impala debug web user interface. You
- configure regular expressions that match sensitive types of information processed by
- your system, such as credit card numbers or tax IDs, and literals matching these
- patterns are obfuscated wherever they would normally be recorded in log files or
- displayed in administration or debugging user interfaces.
- </p>
+ <term>Log redaction</term> is a security feature that prevents sensitive
+ information from being displayed in locations used by administrators for
+ monitoring and troubleshooting, such as log files and the Impala debug
+ web user interface. You configure regular expressions that match
+ sensitive types of information processed by your system, such as credit
+ card numbers or tax IDs, and literals matching these patterns are
+ obfuscated wherever they would normally be recorded in log files or
+ displayed in administration or debugging user interfaces. </p>
<p>
In a security context, the log redaction feature is complementary to the Sentry