Skip to content
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

Jump to bottom

Update logs navigation #3795

Merged
merged 3 commits into from
Apr 17, 2024
Merged

Update logs navigation #3795

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d4f0e1
update logs navigation
mdbirnstiehl Apr 16, 2024
cbf909d
delete screenshot
mdbirnstiehl Apr 16, 2024
251faa7
review comments
mdbirnstiehl Apr 17, 2024
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
Binary file removed docs/en/observability/images/log-explorer.png
View file
Open in desktop
Binary file not shown.
10 changes: 3 additions & 7 deletions docs/en/observability/logs-checklist.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,9 @@
[[logs-checklist]]
= Logs resource guide

++++
<titleabbrev>Logs</titleabbrev>
++++
= Log monitoring

Logs are an important tool for ensuring the performance and reliability of your applications and infrastructure. They provide important information for debugging, analyzing performance, and managing compliance.

In this guide, you'll find resources for sending log data to {es}, configuring your logs, and analyzing your logs.
Here, you'll find resources for sending log data to {es}, configuring your logs, and analyzing your logs.
mdbirnstiehl marked this conversation as resolved.
Show resolved Hide resolved

[discrete]
[[logs-getting-started-checklist]]
Expand All @@ -21,7 +17,7 @@ To get started ingesting, parsing, and filtering your own data, refer to these p
* *<<logs-parse>>*: break your log messages into meaningful fields that you can use to filter and analyze your data.
* *<<logs-filter-and-aggregate>>*: find specific information in your log data to gain insight and monitor your systems.

The following sections in this guide provide resources to important concepts or advanced use cases for working with your logs.
The following sections provide resources to important concepts or advanced use cases for working with your logs.

[discrete]
[[logs-send-data-checklist]]
Expand Down
18 changes: 5 additions & 13 deletions docs/en/observability/monitor-logs.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,24 +1,16 @@
[[monitor-logs]]
= Log monitoring
= Explore logs

The {logs-app} in {kib} enables you to search, filter, and tail all your logs
ingested into {es}. Instead of having to log into different servers, change
directories, and tail individual files, all your logs are available in the {logs-app}.

Using {agent} integrations, you can ingest logs from Kubernetes, MySQL, and many
more data sources. Log events are indexed into {es} and are sorted from older to newer,
with infinite scrolling in both directions.

Logs Explorer allows you to quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization.

[role="screenshot"]
image::images/log-explorer.png[Screen capture of the Logs Explorer]

Refer to the <<explore-logs>> documentation for more on using Logs Explorer.

There is also live streaming of logs, filtering using auto-complete, and a logs histogram
for quick navigation. You can also use {ml} to detect specific log
anomalies automatically and categorize log messages to quickly identify patterns in your
The {logs-app} also provides:
* live <<tail-logs,streaming of logs>>, filtering using auto-complete, and a logs histogram for quick navigation.
* {ml} to detect specific <<inspect-log-anomalies,log anomalies>> automatically and <<categorize-logs, categorize log messages>> to quickly identify patterns in your
log events.

To view the {logs-app}, go to *{observability} > Logs*.
To view the {logs-app}, go to *{observability} > Logs*.
Loading