mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 09:48:58 -04:00
Your window into the Elastic Stack
872d103b7e
# Backport This will backport the following commits from `main` to `8.x`: - [[Streams 🌊] Add initial telemetry to Streams (#214027)](https://github.com/elastic/kibana/pull/214027) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Chris Cowan","email":"chris@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T19:34:52Z","message":"[Streams 🌊] Add initial telemetry to Streams (#214027)\n\n## Summary\n\nThis PR adds EBT telemetry to the Streams backend and UI. For the\nbackend APIs, we are only measuring latency on the \"write\" endpoints\nthat have the highest potential for being slow:\n\n- `POST /api/streams/{name}/processing/_simulate 2023-10-31`\n- `POST /api/streams/{name}/processing/_suggestions 2023-10-31`\n- `POST /api/streams/{name}/_fork 2023-10-31`\n- `PUT /api/streams/{name}/dashboards/{dashboardId} 2023-10-31`\n- `PUT /api/streams/{name} 2023-10-31`\n- `PUT /api/streams/{name}/_group 2023-10-31`\n- `PUT /api/streams/{name}/_ingest 2023-10-31`\n- `DELETE /api/streams/{name} 2023-10-31`\n- `POST /api/streams/_enable 2023-10-31`\n- `POST /api/streams/_disable 2023-10-31`\n- `POST /api/streams/_resync 2023-10-31`\n\nThis is controlled by an allow list located in the server's telemetry\nclient.\n\nFor the UI, I've added the following tracking:\n\n- **Number of Dashboards associated with a Stream** – This captures the\nstream name and the number of dashboards associated with it. It's\nattached to the dashboard hook, this means that we only track dashboard\ncounts on streams that users are actually using.\n- **Clicks on Dashboards** – This captures the name of the dashboard,\nthe dashboard id, and the stream name\n- **Latency of AI Grok Suggestions** – This captures the name of the\nstream, the field used, the number of suggested patterns, the success\nrates of the suggest patterns, and the connector id of the LLM. This\nwill also capture if the AI returned ZERO suggestions.\n- **When a user accepts an AI Grok Suggestion** – This captures the name\nof the stream, the name of the field, the success rate of the pattern,\nand number of fields detected.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"508c89fc15fd611971d28e8f9434b214a945efcf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Feature:Streams","v9.1.0","v8.19.0"],"title":"[Streams 🌊] Add initial telemetry to Streams","number":214027,"url":"https://github.com/elastic/kibana/pull/214027","mergeCommit":{"message":"[Streams 🌊] Add initial telemetry to Streams (#214027)\n\n## Summary\n\nThis PR adds EBT telemetry to the Streams backend and UI. For the\nbackend APIs, we are only measuring latency on the \"write\" endpoints\nthat have the highest potential for being slow:\n\n- `POST /api/streams/{name}/processing/_simulate 2023-10-31`\n- `POST /api/streams/{name}/processing/_suggestions 2023-10-31`\n- `POST /api/streams/{name}/_fork 2023-10-31`\n- `PUT /api/streams/{name}/dashboards/{dashboardId} 2023-10-31`\n- `PUT /api/streams/{name} 2023-10-31`\n- `PUT /api/streams/{name}/_group 2023-10-31`\n- `PUT /api/streams/{name}/_ingest 2023-10-31`\n- `DELETE /api/streams/{name} 2023-10-31`\n- `POST /api/streams/_enable 2023-10-31`\n- `POST /api/streams/_disable 2023-10-31`\n- `POST /api/streams/_resync 2023-10-31`\n\nThis is controlled by an allow list located in the server's telemetry\nclient.\n\nFor the UI, I've added the following tracking:\n\n- **Number of Dashboards associated with a Stream** – This captures the\nstream name and the number of dashboards associated with it. It's\nattached to the dashboard hook, this means that we only track dashboard\ncounts on streams that users are actually using.\n- **Clicks on Dashboards** – This captures the name of the dashboard,\nthe dashboard id, and the stream name\n- **Latency of AI Grok Suggestions** – This captures the name of the\nstream, the field used, the number of suggested patterns, the success\nrates of the suggest patterns, and the connector id of the LLM. This\nwill also capture if the AI returned ZERO suggestions.\n- **When a user accepts an AI Grok Suggestion** – This captures the name\nof the stream, the name of the field, the success rate of the pattern,\nand number of fields detected.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"508c89fc15fd611971d28e8f9434b214a945efcf"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214027","number":214027,"mergeCommit":{"message":"[Streams 🌊] Add initial telemetry to Streams (#214027)\n\n## Summary\n\nThis PR adds EBT telemetry to the Streams backend and UI. For the\nbackend APIs, we are only measuring latency on the \"write\" endpoints\nthat have the highest potential for being slow:\n\n- `POST /api/streams/{name}/processing/_simulate 2023-10-31`\n- `POST /api/streams/{name}/processing/_suggestions 2023-10-31`\n- `POST /api/streams/{name}/_fork 2023-10-31`\n- `PUT /api/streams/{name}/dashboards/{dashboardId} 2023-10-31`\n- `PUT /api/streams/{name} 2023-10-31`\n- `PUT /api/streams/{name}/_group 2023-10-31`\n- `PUT /api/streams/{name}/_ingest 2023-10-31`\n- `DELETE /api/streams/{name} 2023-10-31`\n- `POST /api/streams/_enable 2023-10-31`\n- `POST /api/streams/_disable 2023-10-31`\n- `POST /api/streams/_resync 2023-10-31`\n\nThis is controlled by an allow list located in the server's telemetry\nclient.\n\nFor the UI, I've added the following tracking:\n\n- **Number of Dashboards associated with a Stream** – This captures the\nstream name and the number of dashboards associated with it. It's\nattached to the dashboard hook, this means that we only track dashboard\ncounts on streams that users are actually using.\n- **Clicks on Dashboards** – This captures the name of the dashboard,\nthe dashboard id, and the stream name\n- **Latency of AI Grok Suggestions** – This captures the name of the\nstream, the field used, the number of suggested patterns, the success\nrates of the suggest patterns, and the connector id of the LLM. This\nwill also capture if the AI returned ZERO suggestions.\n- **When a user accepts an AI Grok Suggestion** – This captures the name\nof the stream, the name of the field, the success rate of the pattern,\nand number of fields detected.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"508c89fc15fd611971d28e8f9434b214a945efcf"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|---|---|---|
| .buildkite | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| kbn_pm | ||
| legacy_rfcs | ||
| licenses | ||
| oas_docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| typings | ||
| x-pack | ||
| .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 | ||
| 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 | ||
| versions.json | ||
| WORKSPACE.bazel | ||
| yarn.lock | ||
Kibana
Kibana is your window into the Elastic Stack. Specifically, it's a browser-based analytics and search dashboard for Elasticsearch.
- Getting Started
- Documentation
- Version Compatibility with Elasticsearch
- Questions? Problems? Suggestions?
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:
- Download the latest version on the Kibana Download Page.
- Learn more about Kibana's features and capabilities on the Kibana Product Page.
- We also offer a hosted version of Kibana on our Cloud Service.
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:
- CONTRIBUTING.md will help you get Kibana up and running.
- If you would like to contribute code, please follow our STYLEGUIDE.mdx.
- For all other questions, check out the FAQ.md and wiki.
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.