diff --git a/.github/workflows/docs-build.yml b/.github/workflows/docs-build.yml index ce98e81ae4..b0eb00e1dc 100644 --- a/.github/workflows/docs-build.yml +++ b/.github/workflows/docs-build.yml @@ -7,7 +7,7 @@ jobs: preview: uses: elastic/docs-builder/.github/workflows/preview-build.yml@main with: - continue-on-error: true + continue-on-error: false strict: false permissions: contents: read diff --git a/explore-analyze/machine-learning/anomaly-detection.md b/explore-analyze/machine-learning/anomaly-detection.md index ddbb652568..bc094722c7 100644 --- a/explore-analyze/machine-learning/anomaly-detection.md +++ b/explore-analyze/machine-learning/anomaly-detection.md @@ -8,9 +8,9 @@ mapped_urls: You can use {{stack}} {{ml-features}} to analyze time series data and identify anomalous patterns in your data set. -* [Finding anomalies](../../../explore-analyze/machine-learning/anomaly-detection/ml-ad-finding-anomalies.md) -* [Tutorial: Getting started with {{anomaly-detect}}](../../../explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md) -* [*Advanced concepts*](../../../explore-analyze/machine-learning/anomaly-detection/ml-ad-concepts.md) -* [*API quick reference*](../../../explore-analyze/machine-learning/anomaly-detection/ml-api-quickref.md) -* [How-tos](../../../explore-analyze/machine-learning/anomaly-detection/anomaly-how-tos.md) -* [*Resources*](../../../explore-analyze/machine-learning/anomaly-detection/ml-ad-resources.md) \ No newline at end of file +* [Finding anomalies](../../explore-analyze/machine-learning/anomaly-detection/ml-ad-finding-anomalies.md) +* [Tutorial: Getting started with {{anomaly-detect}}](../../explore-analyze/machine-learning/anomaly-detection/ml-getting-started.md) +* [*Advanced concepts*](../../explore-analyze/machine-learning/anomaly-detection/ml-ad-concepts.md) +* [*API quick reference*](../../explore-analyze/machine-learning/anomaly-detection/ml-api-quickref.md) +* [How-tos](../../explore-analyze/machine-learning/anomaly-detection/anomaly-how-tos.md) +* [*Resources*](../../explore-analyze/machine-learning/anomaly-detection/ml-ad-resources.md) \ No newline at end of file diff --git a/explore-analyze/machine-learning/anomaly-detection/ml-configuring-transform.md b/explore-analyze/machine-learning/anomaly-detection/ml-configuring-transform.md index dfe420336e..e835b3ed99 100644 --- a/explore-analyze/machine-learning/anomaly-detection/ml-configuring-transform.md +++ b/explore-analyze/machine-learning/anomaly-detection/ml-configuring-transform.md @@ -389,3 +389,5 @@ The preview {{dfeed}} API returns the following results, which show that `41.44` } ] ``` + +$$$ml-configuring-transform8$$$ \ No newline at end of file diff --git a/explore-analyze/query-filter.md b/explore-analyze/query-filter.md index d06f85129c..ef9a56d5ba 100644 --- a/explore-analyze/query-filter.md +++ b/explore-analyze/query-filter.md @@ -24,3 +24,4 @@ If you're just getting started with Elasticsearch, try the hands-on [API quickst When querying your data in Kibana, additional options let you filter the results to just the subset you need. Some of these options are common to most Elastic apps. Check [Filtering in Kibana](/explore-analyze/query-filter/filtering.md) for more details on how to recognize and use them in the UI. +$$$search-analyze-query-languages$$$ diff --git a/explore-analyze/query-filter/filtering.md b/explore-analyze/query-filter/filtering.md index 9b6e623227..ee33aede41 100644 --- a/explore-analyze/query-filter/filtering.md +++ b/explore-analyze/query-filter/filtering.md @@ -25,21 +25,21 @@ Some apps provide more options, such as [Dashboards](../dashboards.md). Display data within a specified time range when your index contains time-based events, and a time-field is configured for the selected [{{data-source}}](../find-and-organize/data-views.md). The default time range is 15 minutes, but you can customize it in [Advanced Settings](https://www.elastic.co/guide/en/kibana/current/advanced-options.html). -1. Click ![calendar icon](../../../images/kibana-time-filter-icon.png). +1. Click ![calendar icon](../../images/kibana-time-filter-icon.png). 2. Choose one of the following: * **Quick select**. Set a time based on the last or next number of seconds, minutes, hours, or other time unit. * **Commonly used**. Select a time range from options such as **Last 15 minutes**, **Today**, and **Week to date**. * **Recently used date ranges**. Use a previously selected data range. * **Refresh every**. Specify an automatic refresh rate. - + :::{image} ../../images/kibana-time-filter.png :alt: Time filter menu :width: 300px ::: 3. To set start and end times, click the bar next to the time filter. In the popup, select **Absolute**, **Relative** or **Now**, then specify the required options. - + :::{image} ../../images/kibana-time-relative.png :alt: Time filter showing relative time :width: 350px @@ -55,4 +55,4 @@ To manually resubmit a search, click the **Refresh** button. This is useful when Structured filters are a more interactive way to create {{es}} queries, and are commonly used when building dashboards that are shared by multiple analysts. Each filter can be disabled, inverted, or pinned across all apps. Each of the structured filters is combined with AND logic on the rest of the query. -![Add filter popup](../../../images/kibana-add-filter-popup.png "") \ No newline at end of file +![Add filter popup](../../images/kibana-add-filter-popup.png "") \ No newline at end of file diff --git a/explore-analyze/query-filter/languages/querydsl.md b/explore-analyze/query-filter/languages/querydsl.md index fb149ea09a..635a08475b 100644 --- a/explore-analyze/query-filter/languages/querydsl.md +++ b/explore-analyze/query-filter/languages/querydsl.md @@ -28,7 +28,7 @@ $$$relevance-scores$$$ **Query DSL** is a full-featured JSON-style query language that enables complex searching, filtering, and aggregations. It is the original and most powerful query language for {{es}} today. -The [`_search` endpoint](/solutions/search/querying-for-search-searching-with-the-search-api.md) accepts queries written in Query DSL syntax. +The [`_search` endpoint](../../../solutions/search/querying-for-search.md) accepts queries written in Query DSL syntax. ### Search and filter with Query DSL [search-analyze-query-dsl-search-filter] diff --git a/raw-migrated-files/toc.yml b/raw-migrated-files/toc.yml index 7e36e3a085..67f4bb0ac7 100644 --- a/raw-migrated-files/toc.yml +++ b/raw-migrated-files/toc.yml @@ -605,10 +605,7 @@ toc: - file: elasticsearch/elasticsearch-reference/elasticsearch-intro-deploy.md - file: elasticsearch/elasticsearch-reference/es-ingestion-overview.md - file: elasticsearch/elasticsearch-reference/es-security-principles.md - - file: elasticsearch/elasticsearch-reference/esql-examples.md - - file: elasticsearch/elasticsearch-reference/esql-getting-started.md - file: elasticsearch/elasticsearch-reference/esql-using.md - - file: elasticsearch/elasticsearch-reference/esql.md - file: elasticsearch/elasticsearch-reference/field-and-document-access-control.md - file: elasticsearch/elasticsearch-reference/field-level-security.md - file: elasticsearch/elasticsearch-reference/file-realm.md @@ -638,8 +635,6 @@ toc: - file: elasticsearch/elasticsearch-reference/oidc-guide.md - file: elasticsearch/elasticsearch-reference/oidc-realm.md - file: elasticsearch/elasticsearch-reference/overview-index-lifecycle-management.md - - file: elasticsearch/elasticsearch-reference/query-dsl.md - - file: elasticsearch/elasticsearch-reference/query-filter-context.md - file: elasticsearch/elasticsearch-reference/recovery-prioritization.md - file: elasticsearch/elasticsearch-reference/retrievers-overview.md - file: elasticsearch/elasticsearch-reference/role-mapping-resources.md diff --git a/solutions/observability/cloud/monitor-microsoft-azure-openai.md b/solutions/observability/cloud/monitor-microsoft-azure-openai.md index 8795185bb7..6808bb5225 100644 --- a/solutions/observability/cloud/monitor-microsoft-azure-openai.md +++ b/solutions/observability/cloud/monitor-microsoft-azure-openai.md @@ -486,4 +486,4 @@ Now that you know how to find and visualize your Azure OpenAI logs and metrics, * **Alerts**: Create threshold rules to notify you when your metrics or logs reach or exceed a specified value: Refer to [Metric threshold](../incident-management/create-metric-threshold-rule.md) and [Log threshold](../incident-management/create-log-threshold-rule.md) for more on setting up alerts. * **SLOs**: Set measurable targets for your Azure OpenAI service performance based on your metrics. Once defined, you can monitor your SLOs with dashboards and alerts and track their progress against your targets over time. Refer to [Service-level objectives (SLOs)](../incident-management/service-level-objectives-slos.md) for more on setting up and tracking SLOs. -* **Machine learning (ML) jobs**: Set up ML jobs to find anomalous events and patterns in your Azure OpenAI data. Refer to [Finding anomalies](../../../explore-analyze/machine-learning/anomaly-detection/ml-ad-finding-anomalies.md) for more on setting up ML jobs. +* **Machine learning (ML) jobs**: Set up ML jobs to find anomalous events and patterns in your Azure OpenAI data. Refer to [Finding anomalies](../../../explore-analyze/machine-learning/anomaly-detection/ml-ad-finding-anomalies.md) for more on setting up ML jobs. \ No newline at end of file diff --git a/solutions/search/serverless-elasticsearch-get-started.md b/solutions/search/serverless-elasticsearch-get-started.md index 01abe3bf50..f15f5ccbe2 100644 --- a/solutions/search/serverless-elasticsearch-get-started.md +++ b/solutions/search/serverless-elasticsearch-get-started.md @@ -88,7 +88,7 @@ The UI provides ready-to-use code examples for ingesting data via the REST API. To get started using the in-product tutorial, navigate to the **Getting Started** page and follow the on-screen steps. -:::{image} ../../../images/serverless-getting-started-page.png +:::{image} ../../images/serverless-getting-started-page.png :alt: Getting Started page. :::