Skip to content

Commit 063748c

Browse files
Apply suggestions from code review
Co-authored-by: Benjamin Ironside Goldstein <[email protected]>
1 parent 573d648 commit 063748c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

solutions/observability/logs/categorize-log-entries.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Create a {{ml}} job to categorize log messages automatically. {{ml-cap}} observe
2525
1. Open the **Categories** page by finding `Logs / Categories` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). You are prompted to use {{ml}} to create log rate categorizations.
2626
2. Choose a time range for the {{ml}} analysis. By default, the {{ml}} job analyzes log messages no older than four weeks and continues indefinitely.
2727
3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs sources** advanced setting. 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).
28-
4. Click **Create ML job**. The job is created, and it starts to run. It takes a few minutes for the {{ml}} robots to collect the necessary data. After the job has processed the data, you can view the results.
28+
4. Click **Create ML job**. The creates and runs the job. It takes a few minutes for the {{ml}} robots to collect the necessary data. After the job has processed the data, you can view its results.
2929

3030

3131
## Analyze log categories [analyze-log-categories]
@@ -45,7 +45,7 @@ The category row contains the following information:
4545
* datasets: the name of the datasets where the categories are present.
4646
* maximum anomaly score: the highest anomaly score in the category.
4747

48-
To view a log message under a particular category, click the arrow at the end of the row. To further examine a message, it can be viewed in **Discover** or displayed in its context.
48+
To view a log message for a particular category, click the arrow at the end of the row. To further examine it, click **View in Discover** or **View in context**
4949

5050
:::{image} /solutions/images/observability-log-opened.png
5151
:alt: Opened log category

solutions/observability/logs/inspect-log-anomalies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Create a {{ml}} job to detect anomalous log entry rates automatically.
3030
1. From the main menu, go to **Other tools****Logs Anomalies**, or find `Logs anomalies` in the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). From here, you’ll be prompted to create a {{ml}} job which will carry out the log rate analysis.
3131
2. Choose a time range for the {{ml}} analysis.
3232
3. Add the indices that contain the logs you want to examine. By default, Machine Learning analyzes messages in all log indices that match the patterns set in the **logs source** advanced setting. 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).
33-
4. Click **Create ML job**. The job is created, and it starts to run. It takes a few minutes for the {{ml}} robots to collect the necessary data. After the job has processed the data, you can view the results.
33+
4. Click **Create ML job**. This creates and runs the job. It takes a few minutes for the {{ml}} robots to collect the necessary data. After the job has processed the data, you can view its results.
3434

3535
## Anomalies chart [anomalies-chart]
3636

0 commit comments

Comments
 (0)