fix links"

git push

Author: shainaraskas

deploy-manage/deploy/self-managed/local-development-installation-quickstart.md

@@ -7,5 +7,7 @@ applies_to:
     self:
 ---
 
+# Local development installation (quickstart) [run-elasticsearch-locally]
+
 :::{include} /deploy-manage/deploy/self-managed/_snippets/start-local.md
 :::

explore-analyze/alerts-cases/alerts/alerting-setup.md

@@ -16,7 +16,7 @@ mapped_pages:
 If you are using an **on-premises** {{stack}} deployment:
 
 * In the `kibana.yml` configuration file, add the [`xpack.encryptedSavedObjects.encryptionKey`](kibana://reference/configuration-reference/alerting-settings.md#general-alert-action-settings) setting.
-* For emails to have a footer with a link back to {{kib}}, set the [`server.publicBaseUrl`](../../../deploy-manage/deploy/self-managed/configure.md#server-publicBaseUrl) configuration setting.
+* For emails to have a footer with a link back to {{kib}}, set the [`server.publicBaseUrl`](kibana://reference/configuration-reference/general-settings.md#server-publicBaseUrl) configuration setting.
 
 If you are using an **on-premises** {{stack}} deployment with [**security**](../../../deploy-manage/security.md):
 

explore-analyze/alerts-cases/alerts/rule-action-variables.md

@@ -34,7 +34,7 @@ All rule types pass the following variables:
 :   The date the rule scheduled the action, in ISO format.
 
 `kibanaBaseUrl`
-:   The configured [`server.publicBaseUrl`](../../../deploy-manage/deploy/self-managed/configure.md#server-publicBaseUrl). If not configured, this will be empty.
+:   The configured [`server.publicBaseUrl`](kibana://reference/configuration-reference/general-settings.md#server-publicBaseUrl). If not configured, this will be empty.
 
 `rule.id`
 :   The rule identifier.

explore-analyze/alerts-cases/cases/manage-cases.md

@@ -68,7 +68,7 @@ For self-managed {{kib}}:
          hasAuth: true/false
    ```
 
-3. If you want the email notifications to contain links back to the case, you must configure the [server.publicBaseUrl](../../../deploy-manage/deploy/self-managed/configure.md#server-publicBaseUrl) setting.
+3. If you want the email notifications to contain links back to the case, you must configure the [server.publicBaseUrl](kibana://reference/configuration-reference/general-settings.md#server-publicBaseUrl) setting.
 
 When you subsequently add assignees to cases, they receive an email.
 
@@ -81,7 +81,7 @@ After you create a case, you can upload and manage files on the **Files** tab:
 :screenshot:
 :::
 
-The acceptable file types and sizes are affected by your [case settings](../../../deploy-manage/deploy/self-managed/configure.md).
+The acceptable file types and sizes are affected by your [case settings](kibana://reference/configuration-reference/general-settings.md).
 
 To download or delete the file or copy the file hash to your clipboard, open the action menu (…). The available hash functions are MD5, SHA-1, and SHA-256.
 

explore-analyze/alerts-cases/cases/setup-cases.md

@@ -58,5 +58,5 @@ You can customize sub-feature privileges for deleting cases and comments, editin
 For more details, refer to [{{kib}} privileges](../../../deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
 
 ::::{note}
-If you are using an on-premises {{kib}} deployment and you want the email notifications and the external incident management systems to contain links back to {{kib}}, you must configure the [`server.publicBaseUrl`](../../../deploy-manage/deploy/self-managed/configure.md#server-publicBaseUrl) setting.
+If you are using an on-premises {{kib}} deployment and you want the email notifications and the external incident management systems to contain links back to {{kib}}, you must configure the [`server.publicBaseUrl`](kibana://reference/configuration-reference/general-settings.md#server-publicBaseUrl) setting.
 ::::

explore-analyze/find-and-organize/saved-objects.md

@@ -80,7 +80,7 @@ Import multiple objects in a single operation.
 4. Click **Import**.
 
 ::::{note}
-The [`savedObjects.maxImportExportSize`](/deploy-manage/deploy/self-managed/configure.md#savedObjects-maxImportExportSize) configuration setting limits the number of saved objects to include in the file. The [`savedObjects.maxImportPayloadBytes`](/deploy-manage/deploy/self-managed/configure.md#savedObjects-maxImportPayloadBytes) setting limits the overall size of the file that you can import.
+The [`savedObjects.maxImportExportSize`](kibana://reference/configuration-reference/general-settings.md#savedObjects-maxImportExportSize) configuration setting limits the number of saved objects to include in the file. The [`savedObjects.maxImportPayloadBytes`](kibana://reference/configuration-reference/general-settings.md#savedObjects-maxImportPayloadBytes) setting limits the overall size of the file that you can import.
 ::::
 
 
@@ -94,7 +94,7 @@ Export objects by selection or type.
 {{kib}} creates an NDJSON with all your saved objects. By default, the NDJSON includes child objects related to the saved objects. Exported dashboards include their associated {{data-sources}}.
 
 ::::{note}
-The [`savedObjects.maxImportExportSize`](/deploy-manage/deploy/self-managed/configure.md#savedObjects-maxImportExportSize) configuration setting limits the number of saved objects that you can export.
+The [`savedObjects.maxImportExportSize`](kibana://reference/configuration-reference/general-settings.md#savedObjects-maxImportExportSize) configuration setting limits the number of saved objects that you can export.
 ::::
 
 

explore-analyze/report-and-share/reporting-troubleshooting.md

@@ -62,7 +62,7 @@ Create a Markdown visualization and then create a PDF report. If this succeeds,
 logging.root.level: all
 ```
 
-For more information about logging, check out [Kibana configuration settings](../../deploy-manage/deploy/self-managed/configure.md#logging-root-level).
+For more information about logging, check out [Kibana configuration settings](kibana://reference/configuration-reference/general-settings.md#logging-root-level).
 
 
 

explore-analyze/visualize/manage-panels.md

@@ -72,13 +72,13 @@ There are three types of **Discover** interactions you can add to dashboard pane
 
 * **Panel interactions** — Opens panel data in **Discover**, including the dashboard-level filters, but not the panel-level filters.
 
-    To enable panel interactions, configure [`xpack.discoverEnhanced.actions.exploreDataInContextMenu.enabled`](../../deploy-manage/deploy/self-managed/configure.md#settings-explore-data-in-context) in kibana.yml. If you are using 7.13.0 and earlier, panel interactions are enabled by default.
+    To enable panel interactions, configure [`xpack.discoverEnhanced.actions.exploreDataInContextMenu.enabled`](kibana://reference/configuration-reference/general-settings.md#settings-explore-data-in-context) in kibana.yml. If you are using 7.13.0 and earlier, panel interactions are enabled by default.
 
     To use panel interactions, open the panel menu and click **Explore underlying data**.
 
 * **Series data interactions** — Opens the series data in **Discover**.
 
-    To enable series data interactions, configure [`xpack.discoverEnhanced.actions.exploreDataInChart.enabled`](../../deploy-manage/deploy/self-managed/configure.md#settings-explore-data-in-chart) in kibana.yml. If you are using 7.13.0 and earlier, data series interactions are enabled by default.
+    To enable series data interactions, configure [`xpack.discoverEnhanced.actions.exploreDataInChart.enabled`](kibana://reference/configuration-reference/general-settings.md#settings-explore-data-in-chart) in kibana.yml. If you are using 7.13.0 and earlier, data series interactions are enabled by default.
 
     To use series data interactions, click a data series in the panel.
 

explore-analyze/visualize/maps/maps-connect-to-ems.md

@@ -465,7 +465,7 @@ X-Firefox-Spdy: h2
 
 You might experience EMS connection issues if your Kibana server or browser are on a private network or behind a firewall. If this happens, you can disable the EMS connection to avoid unnecessary EMS requests.
 
-To disable EMS, change your [kibana.yml](../../../deploy-manage/deploy/self-managed/configure.md) file.
+To disable EMS, change your [kibana.yml](kibana://reference/configuration-reference/general-settings.md) file.
 
 1. Set `map.includeElasticMapsService` to `false` to turn off the EMS connection.
 2. Set `map.tilemap.url` to the URL of your tile server. This configures the default tile layer of Maps.
@@ -534,9 +534,9 @@ If you cannot connect to Elastic Maps Service from the {{kib}} server or browser
 
 |     |     |
 | --- | --- |
-| $$$ems-host$$$`host` | Specifies the host of the backend server. To allow remote users to connect, set the value to the IP address or DNS name of the {{hosted-ems}} container. **Default: *your-hostname***. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-host). |
-| `port` | Specifies the port used by the backend server. Default: **`8080`**. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-port). |
-| `basePath` | Specify a path at which to mount the server if you are running behind a proxy. This setting cannot end in a slash (`/`). [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-basePath). |
+| $$$ems-host$$$`host` | Specifies the host of the backend server. To allow remote users to connect, set the value to the IP address or DNS name of the {{hosted-ems}} container. **Default: *your-hostname***. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-host). |
+| `port` | Specifies the port used by the backend server. Default: **`8080`**. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-port). |
+| `basePath` | Specify a path at which to mount the server if you are running behind a proxy. This setting cannot end in a slash (`/`). [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-basePath). |
 | `ui` | Controls the display of the status page and the layer preview. **Default: `true`** |
 | `logging.level` | Verbosity of {{hosted-ems}} logs. Valid values are `trace`, `debug`, `info`, `warn`, `error`, `fatal`, and `silent`. **Default: `info`** |
 | `path.planet` | Path of the basemaps database. **Default: `/usr/src/app/data/planet.mbtiles`** |
@@ -547,19 +547,19 @@ If you cannot connect to Elastic Maps Service from the {{kib}} server or browser
 | --- | --- |
 | `elasticsearch.host` | URL of the {{es}} instance to use for license validation. |
 | `elasticsearch.username` and `elasticsearch.password` | Credentials of a user with at least the `monitor` role. |
-| `elasticsearch.ssl.certificateAuthorities` | Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates that make up a trusted certificate chain for {{hosted-ems}}. This chain is used by {{hosted-ems}} to establish trust when connecting to your {{es}} cluster. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#elasticsearch-ssl-certificateAuthorities). |
-| `elasticsearch.ssl.certificate` and `elasticsearch.ssl.key`, and `elasticsearch.ssl.keyPassphrase` | Optional settings that provide the paths to the PEM-format SSL certificate and key files and the key password. These files are used to verify the identity of {{hosted-ems}} to {{es}} and are required when `xpack.security.http.ssl.client_authentication` in {{es}} is set to `required`. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#elasticsearch-ssl-cert-key). |
-| `elasticsearch.ssl.verificationMode` | Controls the verification of the server certificate that {{hosted-ems}} receives when making an outbound SSL/TLS connection to {{es}}. Valid values are "`full`", "`certificate`", and "`none`". Using "`full`" performs hostname verification, using "`certificate`" skips hostname verification, and using "`none`" skips verification entirely. **Default: `full`**. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#elasticsearch-ssl-verificationMode). |
+| `elasticsearch.ssl.certificateAuthorities` | Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates that make up a trusted certificate chain for {{hosted-ems}}. This chain is used by {{hosted-ems}} to establish trust when connecting to your {{es}} cluster. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#elasticsearch-ssl-certificateAuthorities). |
+| `elasticsearch.ssl.certificate` and `elasticsearch.ssl.key`, and `elasticsearch.ssl.keyPassphrase` | Optional settings that provide the paths to the PEM-format SSL certificate and key files and the key password. These files are used to verify the identity of {{hosted-ems}} to {{es}} and are required when `xpack.security.http.ssl.client_authentication` in {{es}} is set to `required`. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#elasticsearch-ssl-cert-key). |
+| `elasticsearch.ssl.verificationMode` | Controls the verification of the server certificate that {{hosted-ems}} receives when making an outbound SSL/TLS connection to {{es}}. Valid values are "`full`", "`certificate`", and "`none`". Using "`full`" performs hostname verification, using "`certificate`" skips hostname verification, and using "`none`" skips verification entirely. **Default: `full`**. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#elasticsearch-ssl-verificationMode). |
 
 **Server security settings**
 
 |     |     |
 | --- | --- |
-| `ssl.enabled` | Enables SSL/TLS for inbound connections to {{hosted-ems}}. When set to `true`, a certificate and its corresponding private key must be provided. **Default: `false`**. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-ssl-enabled). |
-| `ssl.certificateAuthorities` | Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates that make up a trusted certificate chain for {{hosted-ems}}. This chain is used by the {{hosted-ems}} to establish trust when receiving inbound SSL/TLS connections from end users. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-ssl-certificateAuthorities). |
-| `ssl.key`, `ssl.certificate`, and `ssl.keyPassphrase` | Location of yor SSL key and certificate files and the password that decrypts the private key that is specified via `ssl.key`. This password is optional, as the key may not be encrypted. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-ssl-cert-key). |
-| `ssl.supportedProtocols` | An array of supported protocols with versions.Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`. **Default: `TLSv1.1`, `TLSv1.2`**. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-ssl-supportedProtocols). |
-| `ssl.cipherSuites` | Details on the format, and the valid options, are available via the[OpenSSL cipher list format documentation](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html#CIPHER-LIST-FORMAT).**Default: `TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256, ECDHE-ECDSA-AES128-GCM-SHA256, ECDHE-RSA-AES256-GCM-SHA384, ECDHE-ECDSA-AES256-GCM-SHA384, DHE-RSA-AES128-GCM-SHA256, ECDHE-RSA-AES128-SHA256, DHE-RSA-AES128-SHA256, ECDHE-RSA-AES256-SHA384, DHE-RSA-AES256-SHA384, ECDHE-RSA-AES256-SHA256, DHE-RSA-AES256-SHA256, HIGH,!aNULL, !eNULL, !EXPORT, !DES, !RC4, !MD5, !PSK, !SRP, !CAMELLIA`**. [Equivalent {{kib}} setting](../../../deploy-manage/deploy/self-managed/configure.md#server-ssl-cipherSuites). |
+| `ssl.enabled` | Enables SSL/TLS for inbound connections to {{hosted-ems}}. When set to `true`, a certificate and its corresponding private key must be provided. **Default: `false`**. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-ssl-enabled). |
+| `ssl.certificateAuthorities` | Paths to one or more PEM-encoded X.509 certificate authority (CA) certificates that make up a trusted certificate chain for {{hosted-ems}}. This chain is used by the {{hosted-ems}} to establish trust when receiving inbound SSL/TLS connections from end users. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-ssl-certificateAuthorities). |
+| `ssl.key`, `ssl.certificate`, and `ssl.keyPassphrase` | Location of yor SSL key and certificate files and the password that decrypts the private key that is specified via `ssl.key`. This password is optional, as the key may not be encrypted. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-ssl-cert-key). |
+| `ssl.supportedProtocols` | An array of supported protocols with versions.Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`. **Default: `TLSv1.1`, `TLSv1.2`**. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-ssl-supportedProtocols). |
+| `ssl.cipherSuites` | Details on the format, and the valid options, are available via the[OpenSSL cipher list format documentation](https://www.openssl.org/docs/man1.1.1/man1/ciphers.html#CIPHER-LIST-FORMAT).**Default: `TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_GCM_SHA256 ECDHE-RSA-AES128-GCM-SHA256, ECDHE-ECDSA-AES128-GCM-SHA256, ECDHE-RSA-AES256-GCM-SHA384, ECDHE-ECDSA-AES256-GCM-SHA384, DHE-RSA-AES128-GCM-SHA256, ECDHE-RSA-AES128-SHA256, DHE-RSA-AES128-SHA256, ECDHE-RSA-AES256-SHA384, DHE-RSA-AES256-SHA384, ECDHE-RSA-AES256-SHA256, DHE-RSA-AES256-SHA256, HIGH,!aNULL, !eNULL, !EXPORT, !DES, !RC4, !MD5, !PSK, !SRP, !CAMELLIA`**. [Equivalent {{kib}} setting](kibana://reference/configuration-reference/general-settings.md#server-ssl-cipherSuites). |
 
 
 #### Bind-mounted configuration [elastic-maps-server-bind-mount-config]
@@ -614,7 +614,7 @@ The available basemaps and boundaries can be explored from the `/maps` endpoint
 
 ### Kibana configuration [elastic-maps-server-kibana]
 
-With {{hosted-ems}} running, add the `map.emsUrl` configuration key in your [kibana.yml](../../../deploy-manage/deploy/self-managed/configure.md) file pointing to the root of the service. This setting will point {{kib}} to request EMS basemaps and boundaries from {{hosted-ems}}. Typically this will be the URL to the [host and port](#ems-host) of {{hosted-ems}}. For example, `map.emsUrl: https://my-ems-server:8080`.
+With {{hosted-ems}} running, add the `map.emsUrl` configuration key in your [kibana.yml](kibana://reference/configuration-reference/general-settings.md) file pointing to the root of the service. This setting will point {{kib}} to request EMS basemaps and boundaries from {{hosted-ems}}. Typically this will be the URL to the [host and port](#ems-host) of {{hosted-ems}}. For example, `map.emsUrl: https://my-ems-server:8080`.
 
 
 ### Status check [elastic-maps-server-check]

explore-analyze/visualize/maps/maps-troubleshooting.md

@@ -47,7 +47,7 @@ Maps uses the [{{es}} vector tile search API](https://www.elastic.co/docs/api/do
     * Ensure your geospatial field is searchable and aggregatable.
     * If your geospatial field type does not match your Elasticsearch mapping, click the **Refresh** button to refresh the field list from Elasticsearch.
 
-* Data views with thousands of fields can exceed the default maximum payload size. Increase [`server.maxPayload`](../../../deploy-manage/deploy/self-managed/configure.md) for large data views.
+* Data views with thousands of fields can exceed the default maximum payload size. Increase [`server.maxPayload`](kibana://reference/configuration-reference/general-settings.md) for large data views.
 
 
 ### Features are not displayed [_features_are_not_displayed]