From f39c71319ea40ae42f8965be1640d53e5a3fd093 Mon Sep 17 00:00:00 2001 From: Puja Jagani Date: Mon, 25 Jan 2021 18:50:02 +0530 Subject: [PATCH] Update trace log level info and sample log --- .../content/grid/grid_4/advanced_features/observability.de.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.en.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.es.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.fr.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.ja.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.ko.md | 4 ++-- .../content/grid/grid_4/advanced_features/observability.nl.md | 4 ++-- .../grid/grid_4/advanced_features/observability.zh-cn.md | 4 ++-- 8 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.de.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.de.md index d07d4fd19699..16ddf70b2c9c 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.de.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.de.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.en.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.en.md index cc48364c290d..adeabc44cfee 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.en.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.en.md @@ -85,7 +85,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -101,7 +101,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.es.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.es.md index b4a733f31f17..f1b2dc714f63 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.es.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.es.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.fr.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.fr.md index 42b5c015f9a0..90efe699e11e 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.fr.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.fr.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.ja.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.ja.md index 10cf24e385e5..a1666e995185 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.ja.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.ja.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.ko.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.ko.md index eaaf4cc8e2ce..fbadea11c6f9 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.ko.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.ko.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.nl.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.nl.md index e4c25212f4d2..d2bfe1a1d216 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.nl.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.nl.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL", diff --git a/docs_source_files/content/grid/grid_4/advanced_features/observability.zh-cn.md b/docs_source_files/content/grid/grid_4/advanced_features/observability.zh-cn.md index fb6ad2e22fad..522cc7bbcd93 100644 --- a/docs_source_files/content/grid/grid_4/advanced_features/observability.zh-cn.md +++ b/docs_source_files/content/grid/grid_4/advanced_features/observability.zh-cn.md @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-.jar info tracing ## Leveraging event logs Tracing has to be enabled for event logging as well, even if one does not wish to export traces to visualize them. **By default, tracing is enabled. No additional parameters need to be passed to see logs on the console.** -All events within a span are logged at INFO level. Error events are logged at WARN level. This includes error events as well. +All events within a span are logged at FINE level. Error events are logged at WARN level. All event logs have the following fields : | Field | Field value | Description | @@ -107,7 +107,7 @@ All event logs have the following fields : - INFO [LoggingOptions$1.lambda$export$1] - { + FINE [LoggingOptions$1.lambda$export$1] - { "traceId": "fc8aef1d44b3cc8bc09eb8e581c4a8eb", "spanId": "b7d3b9865d3ddd45", "spanKind": "INTERNAL",