mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
Your window into the Elastic Stack
c099f33d32
# Backport This will backport the following commits from `main` to `8.x`: - [[Investigation app] add entities route and investigation Contextual Insight (#194432)](https://github.com/elastic/kibana/pull/194432) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dominique Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2024-10-04T17:58:28Z","message":"[Investigation app] add entities route and investigation Contextual Insight (#194432)\n\n## Summary\r\n\r\nAdds a route that can be used to fetch entities related to an\r\ninvestigation.\r\n\r\nThe route fetches associated entities by service name, host name, or\r\ncontainer id. It then identifies the associated indices and datastreams.\r\n\r\nThe discovered entities are passed to the contextual insight to inform\r\nthe LLM.\r\n\r\n\r\n\r\n\r\nThis PR represents the first step in developing an AI-informed\r\nhypothesis at the beginning of the investigation. Over time, further\r\ninsights will be provided to the LLM to deepen it's investigative\r\nanalysis and propose a more helpful root cause hypothesis.\r\n\r\n### Testing\r\n\r\n1. Create some APM data. I'm using the otel demo and triggering a\r\nfailure via the flagd service. Since this is in flux, you can reach out\r\nto me about this workflow. However, you can also create APM data via\r\n`synth-trace`.\r\n2. Create an custom threshold rule that you expect to trigger an alert.\r\nI created mine to using `http.response.status_code: 500 /\r\nhttp.response.status_code : *` and set a low threshold base on the\r\namount of failures in my current test data. Be sure to also group the\r\nalert by `service.name`\r\n3. Wait for the alert to fire, then visit the alert details page and\r\nstart an investigation\r\n4. notice the contextual insight. Expand it to see more information\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4bb435b48560852b37e4de54fb9c05cf5a7f3b1","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-management","v8.16.0"],"number":194432,"url":"https://github.com/elastic/kibana/pull/194432","mergeCommit":{"message":"[Investigation app] add entities route and investigation Contextual Insight (#194432)\n\n## Summary\r\n\r\nAdds a route that can be used to fetch entities related to an\r\ninvestigation.\r\n\r\nThe route fetches associated entities by service name, host name, or\r\ncontainer id. It then identifies the associated indices and datastreams.\r\n\r\nThe discovered entities are passed to the contextual insight to inform\r\nthe LLM.\r\n\r\n\r\n\r\n\r\nThis PR represents the first step in developing an AI-informed\r\nhypothesis at the beginning of the investigation. Over time, further\r\ninsights will be provided to the LLM to deepen it's investigative\r\nanalysis and propose a more helpful root cause hypothesis.\r\n\r\n### Testing\r\n\r\n1. Create some APM data. I'm using the otel demo and triggering a\r\nfailure via the flagd service. Since this is in flux, you can reach out\r\nto me about this workflow. However, you can also create APM data via\r\n`synth-trace`.\r\n2. Create an custom threshold rule that you expect to trigger an alert.\r\nI created mine to using `http.response.status_code: 500 /\r\nhttp.response.status_code : *` and set a low threshold base on the\r\namount of failures in my current test data. Be sure to also group the\r\nalert by `service.name`\r\n3. Wait for the alert to fire, then visit the alert details page and\r\nstart an investigation\r\n4. notice the contextual insight. Expand it to see more information\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4bb435b48560852b37e4de54fb9c05cf5a7f3b1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","labelRegex":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/194432","number":194432,"mergeCommit":{"message":"[Investigation app] add entities route and investigation Contextual Insight (#194432)\n\n## Summary\r\n\r\nAdds a route that can be used to fetch entities related to an\r\ninvestigation.\r\n\r\nThe route fetches associated entities by service name, host name, or\r\ncontainer id. It then identifies the associated indices and datastreams.\r\n\r\nThe discovered entities are passed to the contextual insight to inform\r\nthe LLM.\r\n\r\n\r\n\r\n\r\nThis PR represents the first step in developing an AI-informed\r\nhypothesis at the beginning of the investigation. Over time, further\r\ninsights will be provided to the LLM to deepen it's investigative\r\nanalysis and propose a more helpful root cause hypothesis.\r\n\r\n### Testing\r\n\r\n1. Create some APM data. I'm using the otel demo and triggering a\r\nfailure via the flagd service. Since this is in flux, you can reach out\r\nto me about this workflow. However, you can also create APM data via\r\n`synth-trace`.\r\n2. Create an custom threshold rule that you expect to trigger an alert.\r\nI created mine to using `http.response.status_code: 500 /\r\nhttp.response.status_code : *` and set a low threshold base on the\r\namount of failures in my current test data. Be sure to also group the\r\nalert by `service.name`\r\n3. Wait for the alert to fire, then visit the alert details page and\r\nstart an investigation\r\n4. notice the contextual insight. Expand it to see more information\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e4bb435b48560852b37e4de54fb9c05cf5a7f3b1"}},{"branch":"8.x","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com> |
||
|---|---|---|
| .buildkite | ||
| .devcontainer | ||
| .github | ||
| api_docs | ||
| config | ||
| dev_docs | ||
| docs | ||
| examples | ||
| kbn_pm | ||
| legacy_rfcs | ||
| licenses | ||
| oas_docs | ||
| packages | ||
| plugins | ||
| scripts | ||
| src | ||
| test | ||
| 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.