Merge remote-tracking branch 'upstream/master' into task/olm-switch-f…

…leet-server-feature-flag

.github/CODEOWNERS

@@ -99,6 +99,7 @@
 /src/plugins/dashboard/ @elastic/kibana-presentation
 /src/plugins/input_control_vis/ @elastic/kibana-presentation
 /src/plugins/vis_type_markdown/ @elastic/kibana-presentation
+/src/plugins/presentation_util/ @elastic/kibana-presentation
 /test/functional/apps/dashboard/  @elastic/kibana-presentation
 /x-pack/plugins/canvas/  @elastic/kibana-presentation
 /x-pack/plugins/dashboard_enhanced/ @elastic/kibana-presentation

docs/apm/advanced-queries.asciidoc

@@ -2,42 +2,63 @@
 [[advanced-queries]]
 === Query your data
 
-Querying your APM data is a powerful tool that can make finding bottlenecks in your code even easier.
-Imagine you have a user that complains about a slow response time in a specific service.
-With the query bar, you can easily filter the APM app to only display trace data for that user,
-or, to only show transactions that are slower than a specified time threshold.
+Querying your APM data is an essential tool that can make finding bottlenecks in your code even more straightforward.
 
-[float]
-==== Example APM app queries
+Using the query bar, a powerful data query feature, you can pass advanced queries on your data
+to filter on specific pieces of information you’re interested in.
+
+The query bar comes with a handy autocomplete that helps find the fields and even provides suggestions to the data they include.
+You can select the query bar and hit the down arrow on your keyboard to begin scanning recommendations.
 
-* Exclude response times slower than 2000 ms: `transaction.duration.us > 2000000`
-* Filter by response status code: `context.response.status_code ≥ 400`
-* Filter by single user ID: `context.user.id : 12`
+[float]
+[[apm-app-advanced-queries]]
+=== Querying in the APM app
 
-When querying in the APM app, you're merely searching and selecting data from fields in Elasticsearch documents.
-Queries entered into the query bar are also added as parameters to the URL,
-so it's easy to share a specific query or view with others.
+When querying in the APM app, you’re merely searching and selecting data from fields in {es} documents. Queries entered
+into the query bar are also added as parameters to the URL, so it’s easy to share a specific query or view with others.
 
 When you type, you can begin to see some of the transaction fields available for filtering:
 
 [role="screenshot"]
 image::apm/images/apm-query-bar.png[Example of the Kibana Query bar in APM app in Kibana]
 
-TIP: Read the {kibana-ref}/kuery-query.html[Kibana Query Language Enhancements] documentation to learn more about the capabilities of the {kib} query language.
+[TIP]
+=====
+To learn more about the {kib} query language capabilities, see the {kibana-ref}/kuery-query.html[Kibana Query Language Enhancements] documentation.
+=====
+
+[float]
+[[apm-app-queries]]
+==== APM app queries
+
+APM queries can be handy for removing noise from your data in the <<services,Services>>, <<transactions,Transactions>>,
+<<errors,Errors>>, <<metrics,Metrics>>, and <<traces,Traces>> views.
+
+For example, in the *Services* view, you can quickly view a list of all the instrumented services running on your production
+environment: `service.environment : production`. Or filter the list by including the APM agent's name and the host it’s running on:
+`service.environment : "production" and agent.name : "java" and host.name : "prod-server1"`.
+
+On the *Traces* view, you might want to view failed transaction results from any of your running containers:
+`transaction.result :"FAILURE" and container.id : *`.
+
+On the *Transactions* view, you may want to list only the slower transactions than a specified time threshold: `transaction.duration.us > 2000000`.
+Or filter the list by including the service version and the Kubernetes pod it's running on:
+`transaction.duration.us > 2000000 and service.version : "7.12.0" and kubernetes.pod.name : "pod-5468b47f57-pqk2m"`.
 
 [float]
 [[discover-advanced-queries]]
 === Querying in Discover
 
 Alternatively, you can query your APM documents in {kibana-ref}/discover.html[*Discover*].
-Querying documents in *Discover* works the same way as querying in the APM app,
+Querying documents in *Discover* works the same way as queries in the APM app,
 and *Discover* supports all of the example APM app queries shown on this page.
 
 [float]
-==== Example Discover query
+[[discover-queries]]
+==== Discover queries
 
 One example where you may want to make use of *Discover*,
-is for viewing  _all_ transactions for an endpoint, instead of just a sample.
+is to view  _all_ transactions for an endpoint instead of just a sample.
 
 TIP: Starting in v7.6, you can view ten samples per bucket in the APM app, instead of just one.
 

docs/apm/filters.asciidoc

@@ -6,49 +6,34 @@
 <titleabbrev>Filter data</titleabbrev>
 ++++
 
-APM provides two different ways you can filter your data within the APM App:
-
-* <<global-filters>>
-* <<contextual-filters>>
-
-[[global-filters]]
-==== Global filters
-
-Global filters are ways you can filter any and all data across the APM app.
-They are available in the Services, Transactions, Errors, Metrics, and Traces views,
-and any filter applied will persist as you move between pages.
+Global filters are ways you can filter data across the APM app based on a specific
+time range or environment. They are available in the Services, Transactions, Errors,
+Metrics, and Traces views, and any filter applied will persist as you move between pages.
 
 [role="screenshot"]
 image::apm/images/global-filters.png[Global filters available in the APM app in Kibana]
 
-[float]
-===== Global time range
-
-The <<set-time-filter,global time range filter>> in {kib} restricts APM data to a specific time period.
-
-[float]
-[[query-bar]]
-===== Query bar
+[NOTE]
+=====
+If you prefer to use advanced queries on your data to filter on specific pieces
+of information, see <<advanced-queries,Query your data>>.
+=====
 
-The query bar is a powerful data query feature.
-Similar to the query bar in {kibana-ref}/discover.html[Discover],
-it enables you to pass advanced queries on your data to filter on particular pieces of information that you're interested in.
-It comes with a handy autocomplete that helps find the fields and even provides suggestions to the data they include.
-You can select the query bar and hit the down arrow on your keyboard to begin seeing recommendations.
+[[global-time-range]]
+==== Global time range
 
-See <<query-bar,advanced queries>> for more information and sample queries.
+The <<set-time-filter,global time range filter>> in {kib} restricts APM data to a specific time period.
 
-[float]
 [[environment-selector]]
-===== Service environment filter
+==== Service environment filter
 
 The environment selector is a global filter for `service.environment`.
-It allows you to view only relevant data, and is especially useful for separating development from production environments.
+It allows you to view only relevant data and is especially useful for separating development from production environments.
 By default, all environments are displayed. If there are no environment options, you'll see "not defined".
 
 Service environments are defined when configuring your APM agents.
 It's vital to be consistent when naming environments in your agents.
-See the documentation for each agent you're using to learn how to configure service environments:
+To learn how to configure service environments, see the specific agent documentation:
 
 * *Go:* {apm-go-ref}/configuration.html#config-environment[`ELASTIC_APM_ENVIRONMENT`]
 * *Java:* {apm-java-ref}/config-core.html#config-environment[`environment`]
@@ -58,19 +43,3 @@ See the documentation for each agent you're using to learn how to configure serv
 * *Python:* {apm-py-ref}/configuration.html#config-environment[`environment`]
 * *Ruby:* {apm-ruby-ref}/configuration.html#config-environment[`environment`]
 * *Real User Monitoring:* {apm-rum-ref}/configuration.html#environment[`environment`]
-
-[[contextual-filters]]
-==== Contextual filters
-
-Contextual filters are ways you can filter your specific APM data on each individual page.
-The filters shown are relevant to your data, and will persist between pages,
-but only where they are applicable -- they are typically most useful in their original context.
-As an example, if you select a host on the Services overview, then select a transaction group,
-the host filter will still be applied.
-
-These filters are very useful for quickly and easily removing noise from your data.
-With just a click, you can filter your transactions by the transaction result,
-host, container ID, Kubernetes pod, and more.
-
-[role="screenshot"]
-image::apm/images/local-filter.png[Local filters available in the APM app in Kibana]

docs/development/core/public/kibana-plugin-core-public.doclinksstart.links.md

@@ -100,6 +100,8 @@ readonly links: {
         };
         readonly indexPatterns: {
             readonly introduction: string;
+            readonly fieldFormattersNumber: string;
+            readonly fieldFormattersString: string;
         };
         readonly addData: string;
         readonly kibana: string;

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.esfilters.md

@@ -9,6 +9,7 @@
 ```typescript
 esFilters: {
     FilterLabel: (props: import("./ui/filter_bar/filter_editor/lib/filter_label").FilterLabelProps) => JSX.Element;
+    FilterItem: (props: import("./ui/filter_bar/filter_item").FilterItemProps) => JSX.Element;
     FILTERS: typeof FILTERS;
     FilterStateStore: typeof FilterStateStore;
     buildEmptyFilter: (isPinned: boolean, index?: string | undefined) => import("../common").Filter;

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.querystringinputprops.submitonblur.md

@@ -0,0 +1,11 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-plugins-data-public](./kibana-plugin-plugins-data-public.md) &gt; [QueryStringInputProps](./kibana-plugin-plugins-data-public.querystringinputprops.md) &gt; [submitOnBlur](./kibana-plugin-plugins-data-public.querystringinputprops.submitonblur.md)
+
+## QueryStringInputProps.submitOnBlur property
+
+<b>Signature:</b>
+
+```typescript
+submitOnBlur?: boolean;
+```

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.searchsessioninfoprovider.appendsessionstarttimetoname.md

@@ -0,0 +1,13 @@
+<!-- Do not edit this file. It is automatically generated by API Documenter. -->
+
+[Home](./index.md) &gt; [kibana-plugin-plugins-data-public](./kibana-plugin-plugins-data-public.md) &gt; [SearchSessionInfoProvider](./kibana-plugin-plugins-data-public.searchsessioninfoprovider.md) &gt; [appendSessionStartTimeToName](./kibana-plugin-plugins-data-public.searchsessioninfoprovider.appendsessionstarttimetoname.md)
+
+## SearchSessionInfoProvider.appendSessionStartTimeToName property
+
+Append session start time to a session name, `true` by default
+
+<b>Signature:</b>
+
+```typescript
+appendSessionStartTimeToName?: boolean;
+```

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.searchsessioninfoprovider.md

@@ -16,6 +16,7 @@ export interface SearchSessionInfoProvider<ID extends UrlGeneratorId = UrlGenera
 
 |  Property | Type | Description |
 |  --- | --- | --- |
+|  [appendSessionStartTimeToName](./kibana-plugin-plugins-data-public.searchsessioninfoprovider.appendsessionstarttimetoname.md) | <code>boolean</code> | Append session start time to a session name, <code>true</code> by default |
 |  [getName](./kibana-plugin-plugins-data-public.searchsessioninfoprovider.getname.md) | <code>() =&gt; Promise&lt;string&gt;</code> | User-facing name of the session. e.g. will be displayed in saved Search Sessions management list |
 |  [getUrlGeneratorData](./kibana-plugin-plugins-data-public.searchsessioninfoprovider.geturlgeneratordata.md) | <code>() =&gt; Promise&lt;{</code><br/><code>        urlGeneratorId: ID;</code><br/><code>        initialState: UrlGeneratorStateMapping[ID]['State'];</code><br/><code>        restoreState: UrlGeneratorStateMapping[ID]['State'];</code><br/><code>    }&gt;</code> |  |
 

docs/management/numeral.asciidoc

@@ -10,8 +10,8 @@ Numeral formatting patterns are used in multiple places in {kib}, including:
 
 * <<advanced-options, Advanced settings>>
 * <<field-formatters-numeric, Index pattern formatters>>
-* <<tsvb-advanced-editor, TSVB>>
-* <<canvas, Canvas>>
+* <<tsvb, *TSVB*>>
+* <<canvas, *Canvas*>>
 
 The simplest pattern format is `0`, and the default {kib} pattern is `0,0.[000]`.
 The numeral pattern syntax expresses:

docs/redirects.asciidoc

@@ -163,11 +163,6 @@ This content has moved. See <<discover, **Discover**>>.
 
 This content has moved. See <<discover, **Discover**>>.
 
-[role="exclude",id="lens"]
-== Lens
-
-This content has moved. See <<create-panels-with-lens>>.
-
 [role="exclude",id="known-plugins"]
 == Known plugins
 
@@ -241,7 +236,7 @@ This page has been moved. Refer to <<vega-tutorial-create-a-stacked-area-chart>>
 [[heatmap-chart]]
 === Heatmap Chart
 
-This page has been moved. Refer to <<types-of-visualization-panels>>.
+This page has been moved. Refer to <<types-of-visualizations>>.
 
 [float]
 [[interface-overview]]
@@ -285,3 +280,9 @@ This content has moved. Refer to <<dashboard, **Dashboard**>>.
 == Ingest Node Pipelines
 
 This content has moved. See {ref}/ingest.html[Ingest pipelines].
+
+
+[role="exclude",id="create-panels-with-timelion"]
+== Timelion
+
+This content has moved. refer to <<timelion>>.

docs/user/canvas.asciidoc

@@ -126,7 +126,7 @@ image::images/canvas-element-select.gif[Canvas elements]
 * *{es} documents* &mdash; Access your data in {es} without using aggregations. To use, select an index and fields, and optionally enter a query using the <<lucene-query,Lucene Query Syntax>>. 
 Use the *{es} documents* data source when you have low volume datasets, to view raw documents, or to plot exact, non-aggregated values on a chart.
 
-* *Timelion* &mdash; Access your time series data using <<create-panels-with-timelion,*Timelion*>> queries. To use *Timelion* queries, you can enter a query using the <<lucene-query,Lucene Query Syntax>>.
+* *Timelion* &mdash; Access your time series data using <<timelion,*Timelion*>> queries. To use *Timelion* queries, you can enter a query using the <<lucene-query,Lucene Query Syntax>>.
 +
 Each element can display a different data source, and pages and workpads often contain multiple data sources.