Skip to content

Commit 573d648

Browse files
committed
fix link
1 parent 3201cff commit 573d648

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This feature makes use of {{ml}} {{anomaly-jobs}}. To set up jobs, you must have
2727

2828
Create a {{ml}} job to detect anomalous log entry rates automatically.
2929

30-
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.
30+
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).
3333
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.

0 commit comments

Comments
 (0)