github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 17:59:23 -04:00
Code Issues Projects Releases Packages Wiki Activity
Your window into the Elastic Stack
82240 commits 429 branches 496 tags 23 GiB
Find a file
Kibana Machine b1e03010ab
[8.x] [Response Ops][Alerting] Switch to `logger.warn` for `no_shard_available_action_exception` encountered when collecting telemetry (#205520) (#209323) 
# Backport

This will backport the following commits from `main` to `8.x`:
- [[Response Ops][Alerting] Switch to `logger.warn` for
`no_shard_available_action_exception` encountered when
collecting telemetry
(#205520)](https://github.com/elastic/kibana/pull/205520)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Ying
Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-02-03T14:44:03Z","message":"[Response
Ops][Alerting] Switch to `logger.warn` for
`no_shard_available_action_exception` encountered when collecting
telemetry (#205520)\n\nResolves
https://github.com/elastic/response-ops-team/issues/221\r\n\r\n##
Summary\r\n\r\nLooking through the logs for this, the majority of these
errors have the\r\nfollowing stack trace (14,000+ in the last 7
days):\r\n\r\n```\r\nResponseError:
search_phase_execution_exception\r\n\tRoot
causes:\r\n\t\tno_shard_available_action_exception:
[es-es-search-686bf6b747-xldl8][100.65.77.183:9300][indices:data/read/search[phase/query]]\r\n\t\tno_shard_available_action_exception:
null\r\n at KibanaTransport._request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:543:27)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at
/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:641:32\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:637:20)\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@kbn/core-elasticsearch-client-server-internal/src/create_transport.js:60:16)\r\n
at ClientTraced.SearchApi [as search]
(/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/search.js:72:12)\r\n
at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:42:21)\r\n
at async Promise.all (index 6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nLooking
through the code, we are already catching these errors and\r\nreturning
a default response for that telemetry object.
The\r\n`no_shard_available_action_exception` is not an issue with
Kibana, it's\r\nan ES issue, so this PR catches these types of errors
and log them at a\r\ndebug level instead of a warn level to avoid
polluting the logs with\r\nerrors we have no control
over.\r\n\r\nExcluding those results, we see a different and less
frequent stack\r\ntrace (100+ in the last 15
days):\r\n\r\n```\r\nTypeError: Cannot read properties of undefined
(reading 'by_rule_type_id')\r\n at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:49:109)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at async Promise.all (index
6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nFor
actions telemetry, the volume of these errors is much
lower.\r\nUnfortunately, we are not logging the stack trace for these
errors so\r\nit's harder to track down the source. I've updated the code
to store the\r\nstack trace as well as adding the same handling
for\r\n`no_shard_available_action_exception` under the assumption that
it could\r\nalso be getting these
errors.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4e0c0a785ad8d8d6df66406542acda1189e2b817","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Feature:Actions","Team:ResponseOps","backport:prev-minor","ci:project-deploy-security","v9.1.0","v8.19.0"],"title":"[Response
Ops][Alerting] Switch to `logger.warn` for
`no_shard_available_action_exception` encountered when collecting
telemetry","number":205520,"url":"https://github.com/elastic/kibana/pull/205520","mergeCommit":{"message":"[Response
Ops][Alerting] Switch to `logger.warn` for
`no_shard_available_action_exception` encountered when collecting
telemetry (#205520)\n\nResolves
https://github.com/elastic/response-ops-team/issues/221\r\n\r\n##
Summary\r\n\r\nLooking through the logs for this, the majority of these
errors have the\r\nfollowing stack trace (14,000+ in the last 7
days):\r\n\r\n```\r\nResponseError:
search_phase_execution_exception\r\n\tRoot
causes:\r\n\t\tno_shard_available_action_exception:
[es-es-search-686bf6b747-xldl8][100.65.77.183:9300][indices:data/read/search[phase/query]]\r\n\t\tno_shard_available_action_exception:
null\r\n at KibanaTransport._request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:543:27)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at
/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:641:32\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:637:20)\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@kbn/core-elasticsearch-client-server-internal/src/create_transport.js:60:16)\r\n
at ClientTraced.SearchApi [as search]
(/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/search.js:72:12)\r\n
at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:42:21)\r\n
at async Promise.all (index 6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nLooking
through the code, we are already catching these errors and\r\nreturning
a default response for that telemetry object.
The\r\n`no_shard_available_action_exception` is not an issue with
Kibana, it's\r\nan ES issue, so this PR catches these types of errors
and log them at a\r\ndebug level instead of a warn level to avoid
polluting the logs with\r\nerrors we have no control
over.\r\n\r\nExcluding those results, we see a different and less
frequent stack\r\ntrace (100+ in the last 15
days):\r\n\r\n```\r\nTypeError: Cannot read properties of undefined
(reading 'by_rule_type_id')\r\n at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:49:109)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at async Promise.all (index
6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nFor
actions telemetry, the volume of these errors is much
lower.\r\nUnfortunately, we are not logging the stack trace for these
errors so\r\nit's harder to track down the source. I've updated the code
to store the\r\nstack trace as well as adding the same handling
for\r\n`no_shard_available_action_exception` under the assumption that
it could\r\nalso be getting these
errors.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4e0c0a785ad8d8d6df66406542acda1189e2b817"}},"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/205520","number":205520,"mergeCommit":{"message":"[Response
Ops][Alerting] Switch to `logger.warn` for
`no_shard_available_action_exception` encountered when collecting
telemetry (#205520)\n\nResolves
https://github.com/elastic/response-ops-team/issues/221\r\n\r\n##
Summary\r\n\r\nLooking through the logs for this, the majority of these
errors have the\r\nfollowing stack trace (14,000+ in the last 7
days):\r\n\r\n```\r\nResponseError:
search_phase_execution_exception\r\n\tRoot
causes:\r\n\t\tno_shard_available_action_exception:
[es-es-search-686bf6b747-xldl8][100.65.77.183:9300][indices:data/read/search[phase/query]]\r\n\t\tno_shard_available_action_exception:
null\r\n at KibanaTransport._request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:543:27)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at
/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:641:32\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:637:20)\r\n
at KibanaTransport.request
(/usr/share/kibana/node_modules/@kbn/core-elasticsearch-client-server-internal/src/create_transport.js:60:16)\r\n
at ClientTraced.SearchApi [as search]
(/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/search.js:72:12)\r\n
at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:42:21)\r\n
at async Promise.all (index 6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nLooking
through the code, we are already catching these errors and\r\nreturning
a default response for that telemetry object.
The\r\n`no_shard_available_action_exception` is not an issue with
Kibana, it's\r\nan ES issue, so this PR catches these types of errors
and log them at a\r\ndebug level instead of a warn level to avoid
polluting the logs with\r\nerrors we have no control
over.\r\n\r\nExcluding those results, we see a different and less
frequent stack\r\ntrace (100+ in the last 15
days):\r\n\r\n```\r\nTypeError: Cannot read properties of undefined
(reading 'by_rule_type_id')\r\n at getTotalAlertsCountAggregations
(/usr/share/kibana/node_modules/@kbn/alerting-plugin/server/usage/lib/get_telemetry_from_alerts.js:49:109)\r\n
at processTicksAndRejections
(node:internal/process/task_queues:95:5)\r\n at async Promise.all (index
6)\r\n at TaskManagerRunner.run
(/usr/share/kibana/node_modules/@kbn/task-manager-plugin/server/task_running/task_runner.js:325:22)\r\n```\r\n\r\nFor
actions telemetry, the volume of these errors is much
lower.\r\nUnfortunately, we are not logging the stack trace for these
errors so\r\nit's harder to track down the source. I've updated the code
to store the\r\nstack trace as well as adding the same handling
for\r\n`no_shard_available_action_exception` under the assumption that
it could\r\nalso be getting these
errors.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine
<elasticmachine@users.noreply.github.com>","sha":"4e0c0a785ad8d8d6df66406542acda1189e2b817"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ying Mao <ying.mao@elastic.co>
2025-02-03 17:48:11 +01:00
.buildkite [8.x] [ci] Increase Checks disk size (#209198) (#209202) 2025-01-31 20:10:44 -06:00
.devcontainer [8.x] Sync devcontainer with main (#202854) 2024-12-03 17:10:40 -08:00
.github [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00
api_docs [8.x] [AVC Banner] Updates the AVC Banner for 2025 (#205467) (#205820) 2025-01-08 11:11:46 -05:00
config [8.x] [FTR][Synonyms UI] Add Synonyms overview FTRs (#208723) (#208925) 2025-01-30 15:12:45 +01:00
dev_docs [8.x] SKA: Update repository structure documentation (#208691) (#208831) 2025-01-30 12:40:53 +03:00
docs [8.x] [Synthetics] Clarify private location api docs !! (#208504) (#209005) 2025-01-30 18:16:42 +00:00
examples [8.x] [Embeddable] EUI Visual Refresh Integration (#204452) (#208565) 2025-01-29 14:47:30 -05:00
kbn_pm [8.x] Sustainable Kibana Architecture: Move CodeEditor related packages #205587 (#205738) (#205919) 2025-01-10 11:20:26 +00:00
legacy_rfcs [8.x] SKA: Update broken references and URLs (#206836) (#208479) 2025-01-28 10:09:09 +01:00
licenses Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
oas_docs [8.x] [Detection Engine] [Alerting] [Response Ops] Rule gaps (#206313) (#208971) 2025-01-30 17:49:06 +01:00
packages [8.x] [scout] add script to discover playwright configs in repo (#208733) (#208886) 2025-01-30 11:34:03 +01:00
plugins
scripts [8.x] SKA: Update broken references and URLs (#206836) (#208479) 2025-01-28 10:09:09 +01:00
src [8.x] [Vega] Fix highlight for HJSON (#208858) (#209292) 2025-02-03 16:43:26 +01:00
test [8.x] [Vega] Fix highlight for HJSON (#208858) (#209292) 2025-02-03 16:43:26 +01:00
typings [8.x] make emotion typing global (#200958) (#203162) 2024-12-05 14:10:16 -06:00
x-pack [8.x] [Response Ops][Alerting] Switch to &#x60;logger.warn&#x60; for &#x60;no_shard_available_action_exception&#x60; encountered when collecting telemetry (#205520) (#209323) 2025-02-03 17:48:11 +01:00
.backportrc.json chore(NA): adds 8.16 into backportrc (#187530) 2024-07-04 19:09:25 +01:00
.bazelignore Remove references to deleted .ci folder (#177168) 2024-02-20 19:54:21 +01:00
.bazeliskversion chore(NA): upgrade bazelisk into v1.11.0 (#125070) 2022-02-09 20:43:57 +00:00
.bazelrc chore(NA): use new and more performant BuildBuddy servers (#130350) 2022-04-18 02:01:38 +01:00
.bazelrc.common Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
.bazelversion chore(NA): revert bazel upgrade for v5.2.0 (#135096) 2022-06-24 03:57:21 +01:00
.browserslistrc Add Firefox ESR to browserlistrc (#184462) 2024-05-29 17:53:18 -05:00
.editorconfig
.eslintignore [8.x] SKA: Fix outdated eslint rules (#206961) (#208486) 2025-01-28 14:46:39 +01:00
.eslintrc.js [8.x] SKA: Update repository structure documentation (#208691) (#208831) 2025-01-30 12:40:53 +03:00
.gitattributes
.gitignore [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-operations (#202739) (#205320) 2024-12-31 19:01:38 +01:00
.i18nrc.json [8.x] [Discover] In-table search (#206454) (#208868) 2025-01-30 09:16:33 +01:00
.node-version [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
.npmrc [npmrc] Fix puppeteer_skip_download configuration (#177673) 2024-02-22 18:59:01 -07:00
.nvmrc [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
.prettierignore
.prettierrc
.puppeteerrc Add .puppeteerrc (#179847) 2024-04-03 09:14:39 -05:00
.stylelintignore
.stylelintrc Bump stylelint to ^14 (#136693) 2022-07-20 10:11:00 -05:00
.telemetryrc.json [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/kibana-core (#201653) (#205563) 2025-01-05 16:32:00 +01:00
.yarnrc
BUILD.bazel Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
catalog-info.yaml [sonarqube] Disable cron (#190611) 2024-08-15 09:19:09 -05:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FAQ.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
fleet_packages.json [8.x] Sync bundled packages with Package Storage (#208241) 2025-01-27 13:05:25 +01:00
github_checks_reporter.json
kibana.d.ts Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
LICENSE.txt Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
NOTICE.txt [8.x] [ES|QL] capitalize &#x60;FROM&#x60; in recommended queries (#205122) (#205352) 2025-01-02 04:27:03 -06:00
package.json [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00
preinstall_check.js Adds AGPL 3.0 license (#192025) 2024-09-06 19:02:41 -06:00
README.md
renovate.json [8.x] [Renovate/Core] Use prev-minor backport strategy (#204709) (#204909) 2024-12-19 11:00:04 +00:00
RISK_MATRIX.mdx
run_fleet_setup_parallel.sh [8.x] Sustainable Kibana Architecture: Move modules owned by @elastic/fleet (#202422) (#205145) 2024-12-24 15:17:23 -06:00
SECURITY.md
sonar-project.properties [sonarqube] update memory, cpu (#190547) 2024-09-09 16:16:30 -05:00
STYLEGUIDE.mdx [styleguide] update path to scss theme (#140742) 2022-09-15 10:41:14 -04:00
tsconfig.base.json [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00
tsconfig.browser.json
tsconfig.browser_bazel.json
tsconfig.json Transpile packages on demand, validate all TS projects (#146212) 2022-12-22 19:00:29 -06:00
TYPESCRIPT.md Fix small typos in the root md files (#134609) 2022-06-23 09:36:11 -05:00
versions.json [ci] Update version tracking for 7.17.25 (#192477) 2024-09-10 20:54:04 -05:00
WORKSPACE.bazel [8.x] Upgrade Node.js to 20.18.2 (#207431) (#207894) 2025-01-22 19:37:48 +00:00
yarn.lock [8.x] Introduce the InferenceChatModel for langchain (#206429) (#209277) 2025-02-03 16:32:00 +01:00

README.md

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.