Skip to content
Open
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ The results on this page might be different than the actual values you get when

The {{kib}} sample data sets include some pre-configured {{anomaly-jobs}} for you to play with. You can use either of the following methods to add the jobs:

* After you load the sample web logs data set on the {{kib}} home page, click **View data** > **ML jobs**.
* Load the sample web logs data set, then click **View data** > **ML jobs**. To access the sample date in {{ech}}, go to the {{kib}} home page, click **Other sample data sets**, then go to the sample web logs card in the expanded section and click **Add data**. To access the sample data in {{serverless-short}}, go to the **Integrations** page in the navigation menu or using the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md), and search for "Sample Data".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is already stated in the prerequisites. Perhaps we should instead rename the "try it out" section to requirements to be more explicit and not have to repeat how to get the sample data?

I am also not sure why we need to just mention ECH here, as I don't understand this page to be ECH specific and the described method is not valid just for ECH.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RE you question about specifying ECH:
This change was made to address feedback a user provided on the solutions nav in Serverless. My interpretation of their comments were that they couldn't find the sample data in Serverless, so I clarified it with this change.

* In the Machine Learning app, when you select the `kibana_sample_data_logs` {{data-sources}} in the **Data Visualizer** or the **Anomaly Detection** job wizards, it recommends that you create a job using its known configuration. Select the **Kibana sample data web logs** configuration.
* Accept the default values and click **Create Jobs**.

Expand All @@ -101,7 +101,7 @@ For more information, see [{{dfeeds-cap}}](ml-ad-run-jobs.md#ml-ad-datafeeds), [

::::

If you want to see all of the configuration details for your jobs and {{dfeeds}}, you can do so on the **Stack Management** > **Anomaly Detection Jobs** page. Alternatively, you can see the configuration files in [GitHub](https://github.com/elastic/kibana/tree/master/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/sample_data_weblogs). For the purposes of this tutorial, however, here’s a quick overview of the goal of each job:
If you want to see all of the configuration details for your jobs and {{dfeeds}}, you can do so on the **Stack Management** > **Anomaly Detection Jobs** page, which you can access from the navigation menu or using the [global search bar](/explore-analyze/find-and-organize/find-apps-and-objects.md). Alternatively, you can see the configuration files in [GitHub](https://github.com/elastic/kibana/tree/master/x-pack/platform/plugins/shared/ml/server/models/data_recognizer/modules/sample_data_weblogs). For the purposes of this tutorial, however, here’s a quick overview of the goal of each job:

* `low_request_rate` uses the `low_count` function to find unusually low request rates
* `response_code_rates` uses the `count` function and partitions the analysis by `response.keyword` values to find unusual event rates by HTTP response code
Expand Down
Loading