Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of github.com:elastic/kibana into 2020-03-23-em…
Browse files Browse the repository at this point in the history
…bed-factory-interface
stacey-gammon committed Apr 1, 2020
2 parents 611325f + 2cff8b4 commit cb40ba2
Showing 94 changed files with 5,334 additions and 2,676 deletions.
2 changes: 1 addition & 1 deletion .ci/Jenkinsfile_flaky
Original file line number Diff line number Diff line change
@@ -35,7 +35,7 @@ kibanaPipeline(timeoutMinutes: 180) {
if (!IS_XPACK) {
kibanaPipeline.buildOss()
if (CI_GROUP == '1') {
runbld("./test/scripts/jenkins_build_kbn_tp_sample_panel_action.sh", "Build kbn tp sample panel action for ciGroup1")
runbld("./test/scripts/jenkins_build_kbn_sample_panel_action.sh", "Build kbn tp sample panel action for ciGroup1")
}
} else {
kibanaPipeline.buildXpack()
14 changes: 10 additions & 4 deletions .github/CODEOWNERS
This CODEOWNERS file contains errors

CODEOWNERS errors

  • Unknown owner on line 6: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/lens/ @elastic/kibana-app
  • Unknown owner on line 7: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/graph/ @elastic/kibana-app
  • Unknown owner on line 8: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …legacy/server/url_shortening/ @elastic/kibana-app
  • Unknown owner on line 9: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …rc/legacy/server/sample_data/ @elastic/kibana-app
  • Unknown owner on line 10: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …gins/kibana/public/dashboard/ @elastic/kibana-app
  • Unknown owner on line 11: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ugins/kibana/public/discover/ @elastic/kibana-app
  • Unknown owner on line 12: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …gins/kibana/public/visualize/ @elastic/kibana-app
  • Unknown owner on line 13: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ic/local_application_service/ @elastic/kibana-app
  • Unknown owner on line 14: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …gins/kibana/public/dev_tools/ @elastic/kibana-app
  • Unknown owner on line 15: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …/legacy/core_plugins/metrics/ @elastic/kibana-app
  • Unknown owner on line 16: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …core_plugins/vis_type_vislib/ @elastic/kibana-app
  • Unknown owner on line 17: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …acy/core_plugins/vis_type_xy/ @elastic/kibana-app
  • Unknown owner on line 19: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/home/public @elastic/kibana-app
  • Unknown owner on line 20: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/home/server/*.ts @elastic/kibana-app
  • Unknown owner on line 21: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …plugins/home/server/services/ @elastic/kibana-app
  • Unknown owner on line 23: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ugins/kibana/public/home/*.ts @elastic/kibana-app
  • Unknown owner on line 24: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …ins/kibana/public/home/*.scss @elastic/kibana-app
  • Unknown owner on line 25: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    …/kibana/public/home/np_ready/ @elastic/kibana-app
  • Unknown owner on line 26: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_legacy/ @elastic/kibana-app
  • Unknown owner on line 27: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/timelion/ @elastic/kibana-app
  • Unknown owner on line 28: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/dev_tools/ @elastic/kibana-app
  • Unknown owner on line 29: make sure the team @elastic/kibana-app exists, is publicly visible, and has write access to the repository
    /src/plugins/dashboard/ @elastic/kibana-app
  • Unknown owner on line 32: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ples/url_generators_examples/ @elastic/kibana-app-arch
  • Unknown owner on line 33: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ples/url_generators_explorer/ @elastic/kibana-app-arch
  • Unknown owner on line 34: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /packages/kbn-interpreter/ @elastic/kibana-app-arch
  • Unknown owner on line 35: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/core_plugins/embeddable_api/ @elastic/kibana-app-arch
  • Unknown owner on line 36: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …acy/core_plugins/interpreter/ @elastic/kibana-app-arch
  • Unknown owner on line 37: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …cy/core_plugins/kibana_react/ @elastic/kibana-app-arch
  • Unknown owner on line 38: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …ins/kibana/public/management/ @elastic/kibana-app-arch
  • Unknown owner on line 39: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …server/routes/api/management/ @elastic/kibana-app-arch
  • Unknown owner on line 40: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/core_plugins/visualizations/ @elastic/kibana-app-arch
  • Unknown owner on line 41: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …legacy/server/index_patterns/ @elastic/kibana-app-arch
  • Unknown owner on line 42: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …rc/plugins/advanced_settings/ @elastic/kibana-app-arch
  • Unknown owner on line 43: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/bfetch/ @elastic/kibana-app-arch
  • Unknown owner on line 44: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/data/ @elastic/kibana-app-arch
  • Unknown owner on line 45: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/embeddable/ @elastic/kibana-app-arch
  • Unknown owner on line 46: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/expressions/ @elastic/kibana-app-arch
  • Unknown owner on line 47: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/inspector/ @elastic/kibana-app-arch
  • Unknown owner on line 48: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_react/ @elastic/kibana-app-arch
  • Unknown owner on line 49: make sure the team @elastic/kibana-canvas exists, is publicly visible, and has write access to the repository
    …bana_react/public/code_editor @elastic/kibana-canvas
  • Unknown owner on line 50: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/kibana_utils/ @elastic/kibana-app-arch
  • Unknown owner on line 51: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/management/ @elastic/kibana-app-arch
  • Unknown owner on line 52: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/navigation/ @elastic/kibana-app-arch
  • Unknown owner on line 53: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/share/ @elastic/kibana-app-arch
  • Unknown owner on line 54: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/ui_actions/ @elastic/kibana-app-arch
  • Unknown owner on line 55: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /src/plugins/visualizations/ @elastic/kibana-app-arch
  • Unknown owner on line 56: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …/plugins/advanced_ui_actions/ @elastic/kibana-app-arch
  • Unknown owner on line 57: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/data_enhanced/ @elastic/kibana-app-arch
  • Unknown owner on line 58: make sure the team @elastic/kibana-app-arch exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/drilldowns/ @elastic/kibana-app-arch
  • Unknown owner on line 66: make sure @watson exists and has write access to the repository
    /src/apm.js @watson
  • Unknown owner on line 69: make sure the team @elastic/beats exists, is publicly visible, and has write access to the repository
    …cy/plugins/beats_management/  @elastic/beats
  • Unknown owner on line 72: make sure the team @elastic/kibana-canvas exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/canvas/  @elastic/kibana-canvas
  • Unknown owner on line 75: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    /x-pack/legacy/plugins/infra/ @elastic/logs-metrics-ui
  • Unknown owner on line 76: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/infra/ @elastic/logs-metrics-ui
  • Unknown owner on line 77: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …-pack/plugins/ingest_manager/ @elastic/ingest-management
  • Unknown owner on line 78: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …egacy/plugins/ingest_manager/ @elastic/ingest-management
  • Unknown owner on line 79: make sure the team @elastic/ingest-management exists, is publicly visible, and has write access to the repository
    …lastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 79: make sure the team @elastic/logs-metrics-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/observability/ @elastic/logs-metrics-ui @elastic/apm-ui @elastic/uptime @elastic/ingest-management
  • Unknown owner on line 80: make sure the team @elastic/stack-monitoring-ui exists, is publicly visible, and has write access to the repository
    …ck/legacy/plugins/monitoring/ @elastic/stack-monitoring-ui
  • Unknown owner on line 90: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ns/transform/  @elastic/ml-ui @elastic/es-ui
  • Unknown owner on line 122: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/core/  @elastic/kibana-platform
  • Unknown owner on line 123: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /config/kibana.yml @elastic/kibana-platform
  • Unknown owner on line 124: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/features/  @elastic/kibana-platform
  • Unknown owner on line 125: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/licensing/  @elastic/kibana-platform
  • Unknown owner on line 126: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /packages/kbn-config-schema/ @elastic/kibana-platform
  • Unknown owner on line 127: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/config/ @elastic/kibana-platform
  • Unknown owner on line 128: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/http/ @elastic/kibana-platform
  • Unknown owner on line 129: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/i18n/ @elastic/kibana-platform
  • Unknown owner on line 130: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/logging/ @elastic/kibana-platform
  • Unknown owner on line 131: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …legacy/server/saved_objects/  @elastic/kibana-platform
  • Unknown owner on line 132: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/legacy/server/status/ @elastic/kibana-platform
  • Unknown owner on line 133: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    /src/plugins/status_page/ @elastic/kibana-platform
  • Unknown owner on line 134: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …ins/saved_objects_management/ @elastic/kibana-platform
  • Unknown owner on line 135: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …heck_published_api_changes.ts @elastic/kibana-platform
  • Unknown owner on line 138: make sure the team @elastic/kibana-platform exists, is publicly visible, and has write access to the repository
    …sp/  @elastic/kibana-security @elastic/kibana-platform
  • Unknown owner on line 151: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    /packages/kbn-analytics/ @elastic/pulse
  • Unknown owner on line 152: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …egacy/core_plugins/ui_metric/ @elastic/pulse
  • Unknown owner on line 153: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    /src/plugins/telemetry/ @elastic/pulse
  • Unknown owner on line 154: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …telemetry_collection_manager/ @elastic/pulse
  • Unknown owner on line 155: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …telemetry_management_section/ @elastic/pulse
  • Unknown owner on line 156: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …src/plugins/usage_collection/ @elastic/pulse
  • Unknown owner on line 157: make sure the team @elastic/pulse exists, is publicly visible, and has write access to the repository
    …s/telemetry_collection_xpack/ @elastic/pulse
  • Unknown owner on line 160: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …pack/legacy/plugins/alerting/ @elastic/kibana-alerting-services
  • Unknown owner on line 161: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/actions/ @elastic/kibana-alerting-services
  • Unknown owner on line 162: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/alerting/ @elastic/kibana-alerting-services
  • Unknown owner on line 163: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/actions/ @elastic/kibana-alerting-services
  • Unknown owner on line 164: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/event_log/ @elastic/kibana-alerting-services
  • Unknown owner on line 165: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 166: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …est/alerting_api_integration/ @elastic/kibana-alerting-services
  • Unknown owner on line 167: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …gration/plugins/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 168: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …ion/test_suites/task_manager/ @elastic/kibana-alerting-services
  • Unknown owner on line 169: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …/plugins/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 170: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …/plugins/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 171: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …ssl/apps/triggers_actions_ui/ @elastic/kibana-alerting-services
  • Unknown owner on line 172: make sure the team @elastic/kibana-alerting-services exists, is publicly visible, and has write access to the repository
    …_ssl/fixtures/plugins/alerts/ @elastic/kibana-alerting-services
  • Unknown owner on line 178: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/console/  @elastic/es-ui
  • Unknown owner on line 179: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /src/plugins/es_ui_shared/  @elastic/es-ui
  • Unknown owner on line 180: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …s/cross_cluster_replication/  @elastic/es-ui
  • Unknown owner on line 181: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/index_lifecycle_management/  @elastic/es-ui
  • Unknown owner on line 182: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …cy/plugins/index_management/  @elastic/es-ui
  • Unknown owner on line 183: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/license_management/  @elastic/es-ui
  • Unknown owner on line 184: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …-pack/legacy/plugins/rollup/  @elastic/es-ui
  • Unknown owner on line 185: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …cy/plugins/snapshot_restore/  @elastic/es-ui
  • Unknown owner on line 186: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …y/plugins/upgrade_assistant/  @elastic/es-ui
  • Unknown owner on line 187: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/console_extensions/  @elastic/es-ui
  • Unknown owner on line 188: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/es_ui_shared/  @elastic/es-ui
  • Unknown owner on line 189: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/grokdebugger/  @elastic/es-ui
  • Unknown owner on line 190: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ck/plugins/index_management/  @elastic/es-ui
  • Unknown owner on line 191: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …/plugins/license_management/  @elastic/es-ui
  • Unknown owner on line 192: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …x-pack/plugins/painless_lab/  @elastic/es-ui
  • Unknown owner on line 193: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ack/plugins/remote_clusters/  @elastic/es-ui
  • Unknown owner on line 194: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/rollup/  @elastic/es-ui
  • Unknown owner on line 195: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …pack/plugins/searchprofiler/  @elastic/es-ui
  • Unknown owner on line 196: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …ck/plugins/snapshot_restore/  @elastic/es-ui
  • Unknown owner on line 197: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    …k/plugins/upgrade_assistant/  @elastic/es-ui
  • Unknown owner on line 198: make sure the team @elastic/es-ui exists, is publicly visible, and has write access to the repository
    /x-pack/plugins/watcher/  @elastic/es-ui
Original file line number Diff line number Diff line change
@@ -177,17 +177,23 @@
# Elasticsearch UI
/src/plugins/console/ @elastic/es-ui
/src/plugins/es_ui_shared/ @elastic/es-ui
/x-pack/plugins/console_extensions/ @elastic/es-ui
/x-pack/legacy/plugins/cross_cluster_replication/ @elastic/es-ui
/x-pack/legacy/plugins/index_lifecycle_management/ @elastic/es-ui
/x-pack/legacy/plugins/index_management/ @elastic/es-ui
/x-pack/legacy/plugins/license_management/ @elastic/es-ui
/x-pack/plugins/remote_clusters/ @elastic/es-ui
/x-pack/legacy/plugins/rollup/ @elastic/es-ui
/x-pack/plugins/searchprofiler/ @elastic/es-ui
/x-pack/plugins/painless_lab/ @elastic/es-ui
/x-pack/legacy/plugins/snapshot_restore/ @elastic/es-ui
/x-pack/legacy/plugins/upgrade_assistant/ @elastic/es-ui
/x-pack/plugins/console_extensions/ @elastic/es-ui
/x-pack/plugins/es_ui_shared/ @elastic/es-ui
/x-pack/plugins/grokdebugger/ @elastic/es-ui
/x-pack/plugins/index_management/ @elastic/es-ui
/x-pack/plugins/license_management/ @elastic/es-ui
/x-pack/plugins/painless_lab/ @elastic/es-ui
/x-pack/plugins/remote_clusters/ @elastic/es-ui
/x-pack/plugins/rollup/ @elastic/es-ui
/x-pack/plugins/searchprofiler/ @elastic/es-ui
/x-pack/plugins/snapshot_restore/ @elastic/es-ui
/x-pack/plugins/upgrade_assistant/ @elastic/es-ui
/x-pack/plugins/watcher/ @elastic/es-ui

Binary file modified docs/logs/images/logs-console.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion docs/logs/using.asciidoc
Original file line number Diff line number Diff line change
@@ -38,7 +38,7 @@ Log entries for the specified time appear in the middle of the page. To quickly
[[logs-customize]]
=== Customize your view
Click *Customize* to customize the view.
Here, you can set the scale to use for the minimap timeline, choose whether to wrap long lines, and choose your preferred text size.
Here, you can choose whether to wrap long lines, and choose your preferred text size.

[float]
=== Configuring the data to use for your logs
45 changes: 37 additions & 8 deletions docs/migration/migrate_8_0.asciidoc
Original file line number Diff line number Diff line change
@@ -61,24 +61,53 @@ for example, `logstash-*`.
*Impact:* Use `xpack.security.authc.providers` instead.

[float]
==== `xpack.security.authc.saml.realm` is now mandatory when using the SAML authentication provider
*Details:* Previously Kibana was choosing the appropriate Elasticsearch SAML realm automatically using the `Assertion Consumer Service`
URL that it derived from the actual server address. Starting in 8.0.0, the Elasticsearch SAML realm name that Kibana will use should be
specified explicitly.
==== `xpack.security.authc.providers` has changed value format
*Details:* `xpack.security.authc.providers` setting in the `kibana.yml` has changed value format.

*Impact:* Always define `xpack.security.authc.saml.realm` when using the SAML authentication provider.
*Impact:* Array of provider types as a value is no longer supported, use extended object format instead.

[float]
==== `xpack.security.authc.saml` is no longer valid
*Details:* The deprecated `xpack.security.authc.saml` setting in the `kibana.yml` file has been removed.

*Impact:* Configure SAML authentication providers using `xpack.security.authc.providers.saml.{provider unique name}.*` settings instead.

[float]
==== `xpack.security.authc.oidc` is no longer valid
*Details:* The deprecated `xpack.security.authc.oidc` setting in the `kibana.yml` file has been removed.

*Impact:* Configure OpenID Connect authentication providers using `xpack.security.authc.providers.oidc.{provider unique name}.*` settings instead.

[float]
==== `xpack.security.public` is no longer valid
*Details:* The deprecated `xpack.security.public` setting in the `kibana.yml` file has been removed.
*Details:* Previously Kibana was choosing the appropriate Elasticsearch SAML realm automatically using the `Assertion Consumer Service`
URL that it derived from the actual server address and `xpack.security.public` setting. Starting in 8.0.0, the deprecated `xpack.security.public` setting in the `kibana.yml` file has been removed and the Elasticsearch SAML realm name that Kibana will use should be specified explicitly.

*Impact:* Define `xpack.security.authc.saml.realm` when using the SAML authentication provider instead.
*Impact:* Define `xpack.security.authc.providers.saml.{provider unique name}.realm` when using the SAML authentication providers instead.

[float]
==== `/api/security/v1/saml` endpoint is no longer supported
*Details:* The deprecated `/api/security/v1/saml` endpoint is no longer supported.

*Impact:* Rely on `/api/security/saml/callback` endpoint when using SAML instead. This change should be reflected in Kibana `server.xsrf.whitelist` config as well as in Elasticsearch and Identity Provider SAML settings.
*Impact:* Rely on `/api/security/saml/callback` endpoint when using SAML instead. This change should be reflected in Elasticsearch and Identity Provider SAML settings.

[float]
==== `/api/security/v1/oidc` endpoint is no longer supported
*Details:* The deprecated `/api/security/v1/oidc` endpoint is no longer supported.

*Impact:* Rely on `/api/security/oidc/callback` endpoint when using OpenID Connect instead. This change should be reflected in Elasticsearch and OpenID Connect Provider settings.

[float]
==== `/api/security/v1/oidc` endpoint is no longer supported for Third Party initiated login
*Details:* The deprecated `/api/security/v1/oidc` endpoint is no longer supported for Third Party initiated login.

*Impact:* Rely on `/api/security/oidc/initiate_login` endpoint when using Third Party initiated OpenID Connect login instead. This change should be reflected in Elasticsearch and OpenID Connect Provider settings.

[float]
==== `/api/security/v1/oidc/implicit` endpoint is no longer supported
*Details:* The deprecated `/api/security/v1/oidc/implicit` endpoint is no longer supported.

*Impact:* Rely on `/api/security/oidc/implicit` endpoint when using OpenID Connect Implicit Flow instead. This change should be reflected in OpenID Connect Provider settings.

[float]
=== `optimize` directory is now in the `data` folder
4 changes: 1 addition & 3 deletions docs/setup/settings.asciidoc
Original file line number Diff line number Diff line change
@@ -410,9 +410,7 @@ all http requests to https over the port configured as `server.port`.
supported protocols with versions. Valid protocols: `TLSv1`, `TLSv1.1`, `TLSv1.2`

`server.xsrf.whitelist:`:: It is not recommended to disable protections for
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header. There are some
scenarios where whitelisting is required, however, such as
<<kibana-authentication, SAML and OpenID Connect Single Sign-On setups>>.
arbitrary API endpoints. Instead, supply the `kbn-xsrf` header.
The `server.xsrf.whitelist` setting requires the following format:

[source,text]
Loading

0 comments on commit cb40ba2

Please sign in to comment.