Your window into the Elastic Stack
Find a file
Raya Fratkina fc332241fe
Update advanced-settings.md to clarify space-specific vs global (#224951)
## Summary

The description of space-specific vs global settings was unclear. This
PR cleans up the language around space-specific vs global settings

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...

---------

Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
2025-06-25 10:28:20 -04:00
.buildkite [ci] Only validate next docs on pull requests targeting main (#225185) 2025-06-25 09:21:12 -05:00
.devcontainer
.github
api_docs
config
dev_docs
docs Update advanced-settings.md to clarify space-specific vs global (#224951) 2025-06-25 10:28:20 -04:00
examples
kbn_pm
legacy_rfcs
licenses
oas_docs
packages
plugins
scripts
src [Discover] Align SCSS - Emotion migration part 2 with new guidelines (#224586) 2025-06-25 16:00:47 +02:00
typings
x-pack [Fleet] Update /uninstall_tokens API to use exact matching for policy_id query (#225113) 2025-06-25 07:52:11 -06:00
.backportrc.json
.bazelignore
.bazeliskversion
.bazelrc
.bazelrc.common
.bazelversion
.browserslistrc
.editorconfig
.eslintignore
.eslintrc.js
.gitattributes
.gitignore
.i18nrc.json
.node-version
.npmrc
.nvmrc
.prettierignore
.prettierrc
.puppeteerrc
.stylelintignore
.stylelintrc
.telemetryrc.json
.yarnrc
BUILD.bazel
catalog-info.yaml
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md
fleet_packages.json
github_checks_reporter.json
kibana.d.ts
LICENSE.txt
NOTICE.txt
package.json Remove playwright-chromium package from dependencies (#225221) 2025-06-25 14:36:51 +02:00
preinstall_check.js
README.md
renovate.json
RISK_MATRIX.mdx
run_fleet_setup_parallel.sh
SECURITY.md
sonar-project.properties
STYLEGUIDE.mdx
tsconfig.base.json
tsconfig.browser.json
tsconfig.browser_bazel.json
tsconfig.json
TYPESCRIPT.md
updatecli-compose.yaml
versions.json
WORKSPACE.bazel
yarn.lock Remove playwright-chromium package from dependencies (#225221) 2025-06-25 14:36:51 +02:00

Kibana

Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.

Getting Started

If you just want to try Kibana out, check out the Elastic Stack Getting Started Page to give it a whirl.

If you're interested in diving a bit deeper and getting a taste of Kibana's capabilities, head over to the Kibana Getting Started Page.

Using a Kibana Release

If you want to use a Kibana release in production, give it a test run, or just play around:

Building and Running Kibana, and/or Contributing Code

You might want to build Kibana locally to contribute some code, test out the latest features, or try out an open PR:

Documentation

Visit Elastic.co for the full Kibana documentation.

For information about building the documentation, see the README in elastic/docs.

Version Compatibility with Elasticsearch

Ideally, you should be running Elasticsearch and Kibana with matching version numbers. If your Elasticsearch has an older version number or a newer major number than Kibana, then Kibana will fail to run. If Elasticsearch has a newer minor or patch number than Kibana, then the Kibana Server will log a warning.

Note: The version numbers below are only examples, meant to illustrate the relationships between different types of version numbers.

Situation Example Kibana version Example ES version Outcome
Versions are the same. 7.15.1 7.15.1 💚 OK
ES patch number is newer. 7.15.0 7.15.1 ⚠️ Logged warning
ES minor number is newer. 7.14.2 7.15.0 ⚠️ Logged warning
ES major number is newer. 7.15.1 8.0.0 🚫 Fatal error
ES patch number is older. 7.15.1 7.15.0 ⚠️ Logged warning
ES minor number is older. 7.15.1 7.14.2 🚫 Fatal error
ES major number is older. 8.0.0 7.15.1 🚫 Fatal error

Questions? Problems? Suggestions?

  • If you've found a bug or want to request a feature, please create a GitHub Issue. Please check to make sure someone else hasn't already created an issue for the same topic.
  • Need help using Kibana? Ask away on our Kibana Discuss Forum and a fellow community member or Elastic engineer will be glad to help you out.