-
Notifications
You must be signed in to change notification settings - Fork 39
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f7d9d08
commit 9a9b479
Showing
1 changed file
with
68 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
--- | ||
mapped_pages: | ||
- https://www.elastic.co/guide/en/observability/current/tail-logs.html | ||
--- | ||
|
||
# Logs Stream [tail-logs] | ||
|
||
::::{note} | ||
**There’s a new, better way to explore your logs!** | ||
|
||
The Logs Stream app and dashboard panel are deactivated by default. We recommend viewing and inspecting your logs with [Logs Explorer](logs-explorer.md) as it provides more features, better performance, and more intuitive navigation. | ||
|
||
To activate the Logs Stream app, refer to [Activate Logs Stream](#activate-logs-stream). | ||
|
||
:::: | ||
|
||
|
||
Within the {{logs-app}}, the **Stream** page enables you to monitor all of the log events flowing in from your servers, virtual machines, and containers in a centralized view. You can consider this as a `tail -f` in your browser, along with the power of search. | ||
|
||
Click **Stream Live** to view a continuous flow of log messages in real time, or click **Stop streaming** to view historical logs from a specified time range. | ||
|
||
|
||
## Activate Logs Stream [activate-logs-stream] | ||
|
||
Because [Logs Explorer](logs-explorer.md) is replacing Logs Stream, Logs Stream and the Logs Stream dashboard panel are disabled by default. To activate Logs Stream and the Logs Stream dashboard panel complete the following steps: | ||
|
||
1. To open **Advanced Settings**, find **Stack Management** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). | ||
2. In **Advanced Settings**, enter *Logs Stream* in the search bar. | ||
3. Turn on **Logs Stream**. | ||
|
||
After saving your settings, you’ll see Logs Stream in the Observability navigation, and the Logs Stream dashboard panel will be available. | ||
|
||
|
||
## Filter logs [filter-logs] | ||
|
||
To help you get started with your analysis faster and extract fields from your logs, use the search bar to create structured queries using [{{kib}} Query Language](../../../explore-analyze/query-filter/languages/kql.md). For example, enter `host.hostname : "host1"` to see only the information for `host1`. | ||
|
||
Additionally, click **Highlights** and enter a term you would like to locate within the log events. The Logs histogram, located to the right, highlights the number of discovered terms and when the log event was ingested. This helps you quickly jump between potential areas of interest in large amounts of logs, or from a high level, view when a large number of events occurred. | ||
|
||
|
||
## Inspect log event details [inspect-log-event] | ||
|
||
When you have searched and filtered your logs for a specific log event, you may want to examine the metadata and the structured fields associated with that event. To view the **Log event document details** fly-out, hover over the log event, click **View actions for line**, and then select **View details**. To further enhance the workflow of monitoring logs, the icons next to each field value enable you to filter the logs per that value. | ||
|
||
:::{image} ../../../images/observability-log-event-details.png | ||
:alt: Log event details | ||
:class: screenshot | ||
::: | ||
|
||
|
||
## View contextual logs [view-contextual-logs] | ||
|
||
Once your logs are filtered, and you find an interesting log line, the real context you are looking for is what happened before and after that log line within that data source. For example, you are running containerized applications on a Kubernetes cluster, you filter the logs for the term `error`, and you find an interesting error log line. The context you want is what happened before and after the error line within the logs of this container and application. | ||
|
||
Hover over the log event, click **View actions for line**, and then select **View in context**. The context is preserved and helps you find the root cause as soon as possible. | ||
|
||
:::{image} ../../../images/observability-contextual-logs.png | ||
:alt: Contextual log event | ||
:class: screenshot | ||
::: | ||
|
||
|
||
## Integrate with Uptime and APM [uptime-apm-integration] | ||
|
||
To see other actions related to a log event, click **Actions** in the **Log event document details** fly-out. Depending on the event and the features you have configured, you can: | ||
|
||
* Select **View status in Uptime** to [view related uptime information](../apps/view-monitor-status.md) in the {{uptime-app}}. | ||
* Select **View in APM** to [view corresponding APM traces](../apps/traces-2.md) in the Applications UI. |