Skip to content

Update trace log level info and sample log #621

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 11, 2021
Merged

Update trace log level info and sample log #621

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f39c713
Update trace log level info and sample log
pujagani Jan 25, 2021
e8b1470
Merge branch 'dev' into fix_trace_log
diemol Mar 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.de.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.es.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.fr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.ja.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.ko.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.nl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down
4 changes: 2 additions & 2 deletions docs_source_files/content/grid/grid_4/advanced_features/observability.zh-cn.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ java -jar selenium-server-4.0.0-<selenium-version>.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 |
Expand All @@ -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",
Expand Down