Merge branch 'master' into incorrect-datafeed-start-time-69537

Author: elasticmachine

docs/developer/advanced/development-basepath.asciidoc

@@ -1,5 +1,5 @@
 [[development-basepath]]
-=== Considerations for basepath
+== Considerations for basepath
 
 In dev mode, {kib} by default runs behind a proxy which adds a random path component to its URL.
 

docs/developer/advanced/development-es-snapshots.asciidoc

@@ -1,32 +1,32 @@
 [[development-es-snapshots]]
-=== Daily Elasticsearch Snapshots
+== Daily {es} Snapshots
 
-For local development and CI, {kib}, by default, uses Elasticsearch snapshots that are built daily when running tasks that require Elasticsearch (e.g. functional tests).
+For local development and CI, {kib}, by default, uses {es} snapshots that are built daily when running tasks that require {es} (e.g. functional tests).
 
-A snapshot is just a group of tarballs, one for each supported distribution/architecture/os of Elasticsearch, and a JSON-based manifest file containing metadata about the distributions.
+A snapshot is just a group of tarballs, one for each supported distribution/architecture/os of {es}, and a JSON-based manifest file containing metadata about the distributions.
 
-https://ci.kibana.dev/es-snapshots[A dashboard] is available that shows the current status and compatibility of the latest Elasticsearch snapshots.
+https://ci.kibana.dev/es-snapshots[A dashboard] is available that shows the current status and compatibility of the latest {es} snapshots.
 
-==== Process Overview
+=== Process Overview
 
-1. Elasticsearch snapshots are built for each current tracked branch of {kib}.
+1. {es} snapshots are built for each current tracked branch of {kib}.
 2. Each snapshot is uploaded to a public Google Cloud Storage bucket, `kibana-ci-es-snapshots-daily`.
 ** At this point, the snapshot is not automatically used in CI or local development. It needs to be tested/verified first.
 3. Each snapshot is tested with the latest commit of the corresponding {kib} branch, using the full CI suite.
 4. After CI
 ** If the snapshot passes, it is promoted and automatically used in CI and local development.
-** If the snapshot fails, the issue must be investigated and resolved. A new incompatibility may exist between Elasticsearch and {kib}.
+** If the snapshot fails, the issue must be investigated and resolved. A new incompatibility may exist between {es} and {kib}.
 
-==== Using the latest snapshot
+=== Using the latest snapshot
 
-When developing locally, you may wish to use the most recent Elasticsearch snapshot, even if it's failing CI. To do so, prefix your commands with the follow environment variable:
+When developing locally, you may wish to use the most recent {es} snapshot, even if it's failing CI. To do so, prefix your commands with the follow environment variable:
 
 ["source","bash"]
 -----------
 KBN_ES_SNAPSHOT_USE_UNVERIFIED=true
 -----------
 
-You can use this flag with any command that downloads and runs Elasticsearch snapshots, such as `scripts/es` or the FTR.
+You can use this flag with any command that downloads and runs {es} snapshots, such as `scripts/es` or the FTR.
 
 For example, to run functional tests with the latest snapshot:
 
@@ -35,7 +35,7 @@ For example, to run functional tests with the latest snapshot:
 KBN_ES_SNAPSHOT_USE_UNVERIFIED=true node scripts/functional_tests_server
 -----------
 
-===== For Pull Requests
+==== For Pull Requests
 
 Currently, there is not a way to run your pull request with the latest unverified snapshot without a code change. You can, however, do it with a small code change.
 
@@ -45,9 +45,9 @@ Currently, there is not a way to run your pull request with the latest unverifie
 
 Your pull request should then use the latest snapshot the next time that it runs. Just don't merge the change to `Jenkinsfile`!
 
-==== Google Cloud Storage buckets
+=== Google Cloud Storage buckets
 
-===== kibana-ci-es-snapshots-daily
+==== kibana-ci-es-snapshots-daily
 
 This bucket stores snapshots that are created on a daily basis, and is the primary location used by `kbn-es` to download snapshots.
 
@@ -61,7 +61,7 @@ The file structure for this bucket looks like this:
 * `<version>/archives/<unique id>/*.tar.gz.sha512`
 * `<version>/archives/<unique id>/manifest.json`
 
-===== kibana-ci-es-snapshots-permanent
+==== kibana-ci-es-snapshots-permanent
 
 This bucket stores only the most recently promoted snapshot for each version. Old snapshots are only deleted when new ones are uploaded.
 
@@ -73,18 +73,18 @@ The file structure for this bucket looks like this:
 * `<version>/*.tar.gz.sha512`
 * `<version>/manifest.json`
 
-==== How snapshots are built, tested, and promoted
+=== How snapshots are built, tested, and promoted
 
-Each day, a https://kibana-ci.elastic.co/job/elasticsearch+snapshots+trigger/[Jenkins job] runs that triggers Elasticsearch builds for each currently tracked branch/version. This job is automatically updated with the correct branches whenever we release new versions of {kib}.
+Each day, a https://kibana-ci.elastic.co/job/elasticsearch+snapshots+trigger/[Jenkins job] runs that triggers {es} builds for each currently tracked branch/version. This job is automatically updated with the correct branches whenever we release new versions of {kib}.
 
-===== Build
+==== Build
 
-https://kibana-ci.elastic.co/job/elasticsearch+snapshots+build/[This Jenkins job] builds the Elasticsearch snapshots and uploads them to GCS.
+https://kibana-ci.elastic.co/job/elasticsearch+snapshots+build/[This Jenkins job] builds the {es} snapshots and uploads them to GCS.
 
 The Jenkins job pipeline definition is https://github.com/elastic/kibana/blob/master/.ci/es-snapshots/Jenkinsfile_build_es[in the {kib} repo].
 
-1. Checkout Elasticsearch repo for the given branch/version.
-2. Run `./gradlew -p distribution/archives assemble --parallel` to create all of the Elasticsearch distributions.
+1. Checkout {es} repo for the given branch/version.
+2. Run `./gradlew -p distribution/archives assemble --parallel` to create all of the {es} distributions.
 3. Create a tarball for each distribution.
 4. Create a manifest JSON file containing info about the distribution, as well as its download URL.
 5. Upload the tarballs and manifest to a unique location in the GCS bucket `kibana-ci-es-snapshots-daily`.
@@ -93,9 +93,9 @@ The Jenkins job pipeline definition is https://github.com/elastic/kibana/blob/ma
 ** This allows the `KBN_ES_SNAPSHOT_USE_UNVERIFIED` flag to work.
 7. Trigger the verification job, to run the full {kib} CI test suite with this snapshot.
 
-===== Verification and Promotion
+==== Verification and Promotion
 
-https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/[This Jenkins job] tests the latest Elasticsearch snapshot with the full {kib} CI pipeline, and promotes if it there are no test failures.
+https://kibana-ci.elastic.co/job/elasticsearch+snapshots+verify/[This Jenkins job] tests the latest {es} snapshot with the full {kib} CI pipeline, and promotes if it there are no test failures.
 
 The Jenkins job pipeline definition is https://github.com/elastic/kibana/blob/master/.ci/es-snapshots/Jenkinsfile_verify_es[in the {kib} repo].
 

docs/developer/advanced/index.asciidoc

@@ -5,8 +5,8 @@
 * <<development-es-snapshots>>
 * <<development-basepath>>
 
-include::development-es-snapshots.asciidoc[]
+include::development-es-snapshots.asciidoc[leveloffset=+1]
 
-include::running-elasticsearch.asciidoc[]
+include::running-elasticsearch.asciidoc[leveloffset=+1]
 
-include::development-basepath.asciidoc[]
+include::development-basepath.asciidoc[leveloffset=+1]

docs/developer/advanced/running-elasticsearch.asciidoc

@@ -1,13 +1,13 @@
 [[running-elasticsearch]]
-=== Running elasticsearch during development
+== Running {es} during development
 
-There are many ways to run Elasticsearch while you are developing.
+There are many ways to run {es} while you are developing.
 
-[float]
+[discrete]
 
-==== By snapshot
+=== By snapshot
 
-This will run a snapshot of elasticsearch that is usually built nightly. Read more about <<development-es-snapshots>>.
+This will run a snapshot of {es} that is usually built nightly. Read more about <<development-es-snapshots>>.
 
 [source,bash]
 ----
@@ -25,36 +25,36 @@ yarn es snapshot --help
 
 **Keeping data between snapshots**
 
-If you want to keep the data inside your Elasticsearch between usages of this command, you should use the following command, to keep your data folder outside the downloaded snapshot folder:
+If you want to keep the data inside your {es} between usages of this command, you should use the following command, to keep your data folder outside the downloaded snapshot folder:
 
 [source,bash]
 ----
 yarn es snapshot -E path.data=../data
 ----
 
-==== By source
+=== By source
 
-If you have the Elasticsearch repo checked out locally and wish to run against that, use `source`. By default, it will reference an elasticsearch checkout which is a sibling to the {kib} directory named elasticsearch. If you wish to use a checkout in another location you can provide that by supplying --source-path 
+If you have the {es} repo checked out locally and wish to run against that, use `source`. By default, it will reference an {es} checkout which is a sibling to the {kib} directory named elasticsearch. If you wish to use a checkout in another location you can provide that by supplying --source-path 
 
 [source,bash]
 ----
 yarn es source
 ----
 
-==== From an archive
+=== From an archive
 
-Use this if you already have a distributable. For released versions, one can be obtained on the Elasticsearch downloads page.
+Use this if you already have a distributable. For released versions, one can be obtained on the {es} downloads page.
 
 [source,bash]
 ----
 yarn es archive <full_path_to_archive>
 ----
 
-Each of these will run Elasticsearch with a basic license. Additional options are available, pass --help for more information.
+Each of these will run {es} with a basic license. Additional options are available, pass --help for more information.
 
-==== From a remote host
+=== From a remote host
 
-You can save some system resources, and the effort of generating sample data, if you have a remote Elasticsearch cluster to connect to. (Elasticians: you do! Check with your team about where to find credentials)
+You can save some system resources, and the effort of generating sample data, if you have a remote {es} cluster to connect to. (Elasticians: you do! Check with your team about where to find credentials)
 
 You'll need to create a kibana.dev.yml (<<customize-kibana-yml>>) and add the following to it:
 
@@ -75,7 +75,7 @@ kibana.index: '.{YourGitHubHandle}-kibana'
 xpack.task_manager.index: '.{YourGitHubHandle}-task-manager-kibana'
 ----
 
-===== Running remote clusters
+==== Running remote clusters
 
 Setup remote clusters for cross cluster search (CCS) and cross cluster replication (CCR).
 
@@ -95,7 +95,7 @@ yarn es snapshot -E transport.port=9500 -E http.port=9201 -E path.data=../data_p
 
 Once both clusters are running, start {kib}. {kib} will connect to the primary cluster.
 
-Setup the remote cluster in {kib} from either Management -> Elasticsearch -> Remote Clusters UI or by running the following script in Console.
+Setup the remote cluster in {kib} from either Management -> {es} -> Remote Clusters UI or by running the following script in Console.
 
 [source,bash]
 ----

docs/developer/architecture/add-data-tutorials.asciidoc

@@ -1,16 +1,16 @@
 [[add-data-tutorials]]
-=== Add data tutorials
+== Add data tutorials
 
 `Add Data` in the {kib} Home application contains tutorials for setting up data flows in the Elastic stack.
 
 Each tutorial contains three sets of instructions:
 
-* `On Premise.` Set up a data flow when both {kib} and Elasticsearch are running on premise.
-* `On Premise Elastic Cloud.` Set up a data flow when {kib} is running on premise and Elasticsearch is running on Elastic Cloud.
-* `Elastic Cloud.` Set up a data flow when both {kib} and Elasticsearch are running on Elastic Cloud.
+* `On Premise.` Set up a data flow when both {kib} and {es} are running on premise.
+* `On Premise Elastic Cloud.` Set up a data flow when {kib} is running on premise and {es} is running on Elastic Cloud.
+* `Elastic Cloud.` Set up a data flow when both {kib} and {es} are running on Elastic Cloud.
 
-[float]
-==== Creating a new tutorial
+[discrete]
+=== Creating a new tutorial
 1. Create a new directory in the link:https://github.com/elastic/kibana/tree/master/src/plugins/home/server/tutorials[tutorials directory].
 2. In the new directory, create a file called `index.ts` that exports a function.
 The function must return a function object that conforms to the `TutorialSchema` interface link:{kib-repo}tree/{branch}/src/plugins/home/server/services/tutorials/lib/tutorial_schema.ts[tutorial schema].
@@ -23,15 +23,15 @@ The function must return a function object that conforms to the `TutorialSchema`
 If you are creating a new plugin and the tutorial is only related to that plugin, you can also place the `TutorialSchema` object into your plugin folder. Add `home` to the `requiredPlugins` list in your `kibana.json` file.
 Then register the tutorial object by calling `home.tutorials.registerTutorial(tutorialObject)` in the `setup` lifecycle of your server plugin.
 
-[float]
-===== Variables
+[discrete]
+==== Variables
 String values can contain variables that are substituted when rendered. Variables are specified by `{}`.
 For example: `{config.docs.version}` is rendered as `6.2` when running the tutorial in {kib} 6.2.
 
 link:{kib-repo}tree/{branch}/src/legacy/core_plugins/kibana/public/home/np_ready/components/tutorial/replace_template_strings.js#L23[Provided variables]
 
-[float]
-===== Markdown
+[discrete]
+==== Markdown
 String values can contain limited Markdown syntax.
 
 link:{kib-repo}tree/{branch}/src/legacy/core_plugins/kibana/public/home/components/tutorial/content.js#L8[Enabled Markdown grammars]

docs/developer/architecture/development-visualize-index.asciidoc

@@ -1,5 +1,5 @@
 [[development-visualize-index]]
-=== Developing Visualizations
+== Developing Visualizations
 
 [IMPORTANT]
 ==============================================

docs/developer/architecture/index.asciidoc

@@ -18,8 +18,8 @@ A few notable services are called out below.
 * <<add-data-tutorials>>
 * <<development-visualize-index>>
 
-include::add-data-tutorials.asciidoc[]
+include::add-data-tutorials.asciidoc[leveloffset=+1]
 
-include::development-visualize-index.asciidoc[]
+include::development-visualize-index.asciidoc[leveloffset=+1]
 
-include::security/index.asciidoc[]
+include::security/index.asciidoc[leveloffset=+1]

docs/developer/architecture/security/feature-registration.asciidoc

@@ -1,13 +1,13 @@
 [[development-plugin-feature-registration]]
-==== Plugin feature registration
+== Plugin feature registration
 
 If your plugin will be used with {kib}'s default distribution, then you have the ability to register the features that your plugin provides. Features are typically apps in {kib}; once registered, you can toggle them via Spaces, and secure them via Roles when security is enabled.
 
-===== UI Capabilities
+=== UI Capabilities
 
 Registering features also gives your plugin access to “UI Capabilities”. These capabilities are boolean flags that you can use to conditionally render your interface, based on the current user's permissions. For example, you can  hide or disable a Save button if the current user is not authorized.
 
-===== Registering a feature
+=== Registering a feature
 
 Feature registration is controlled via the built-in `xpack_main` plugin. To register a feature, call `xpack_main`'s `registerFeature` function from your plugin's `init` function, and provide the appropriate details:
 
@@ -21,7 +21,7 @@ init(server) {
 }
 -----------
 
-===== Feature details
+=== Feature details
 Registering a feature consists of the following fields. For more information, consult the {kib-repo}blob/{branch}/x-pack/plugins/features/server/feature_registry.ts[feature registry interface].
 
 
@@ -65,12 +65,12 @@ Registering a feature consists of the following fields. For more information, co
 |The ID of the navigation link associated with your feature.
 |===
 
-====== Privilege definition
+==== Privilege definition
 The `privileges` section of feature registration allows plugins to implement read/write and read-only modes for their applications.
 
 For a full explanation of fields and options, consult the {kib-repo}blob/{branch}/x-pack/plugins/features/server/feature_registry.ts[feature registry interface].
 
-===== Using UI Capabilities
+=== Using UI Capabilities
 
 UI Capabilities are available to your public (client) plugin code. These capabilities are read-only, and are used to inform the UI. This object is namespaced by feature id. For example, if your feature id is “foo”, then your UI Capabilities are stored at `uiCapabilities.foo`.
 To access capabilities, import them from `ui/capabilities`:
@@ -86,7 +86,7 @@ if (canUserSave) {
 -----------
 
 [[example-1-canvas]]
-===== Example 1: Canvas Application
+=== Example 1: Canvas Application
 ["source","javascript"]
 -----------
 init(server) {
@@ -141,7 +141,7 @@ if (canUserSave) {
 Because the `read` privilege does not define the `save` capability, users with read-only access will have their `uiCapabilities.canvas.save` flag set to `false`.
 
 [[example-2-dev-tools]]
-===== Example 2: Dev Tools
+=== Example 2: Dev Tools
 
 ["source","javascript"]
 -----------
@@ -176,7 +176,7 @@ init(server) {
     },
     privilegesTooltip: i18n.translate('xpack.features.devToolsPrivilegesTooltip', {
      defaultMessage:
-       'User should also be granted the appropriate Elasticsearch cluster and index privileges',
+       'User should also be granted the appropriate {es} cluster and index privileges',
    }),
   });
 }
@@ -199,7 +199,7 @@ server.route({
 -----------
 
 [[example-3-discover]]
-===== Example 3: Discover
+=== Example 3: Discover
 
 Discover takes advantage of subfeature privileges to allow fine-grained access control. In this example,
 a single "Create Short URLs" subfeature privilege is defined, which allows users to grant access to this feature without having to grant the `all` privilege to Discover. In other words, you can grant `read` access to Discover, and also grant the ability to create short URLs.