mrkeyoor.comAsk

elastic/kibanatested 11 Nov 2026commit 650d1d3

kibana review

Kibana's build failed after 1 second in our sandbox because its version check rejected Node v24.19.0 and requested v24.22.1.

  • Build failed
52 sto install
  • 1 packages
Dataevaluationupdated 14 Nov 2026
+11stars / 7d

Kibana is Elastic's web interface for querying, analyzing, visualizing and managing data stored in Elasticsearch. It gives teams a way to work with that data through an interface rather than writing every interaction themselves.

Verdict

Kibana's build failed after 1 second in our sandbox because its version check rejected Node v24.19.0 and requested v24.22.1. Choose Kibana when Elasticsearch is already the data platform and you can coordinate their versions. Start a product evaluation with a matching release pair; the failed source build doesn't establish how that pair performs.

We ran it

Lab card: what happened when we ran kibana
Lab card from our sandbox run
Screenshot of kibana (www.elastic.co/products/kibana)
www.elastic.co/products/kibana
Install✓ · 52s1 packages · 2423 MB
Build✗ · 1s
Testsn/ano test script
Repo131803 files~15,186,208 lines of source · 1224.3 MB · 58 CI workflows

Answers from our run

Does kibana build from source?

Dependencies installed in 52 seconds (1 packages), and the build failed. We cloned commit 650d1d3 into a clean Debian container with 3 CPUs and no project-specific setup.

Does kibana have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Who should not use kibana?

Teams expecting a general interface for unrelated databases: the README defines Kibana around data in Elasticsearch.

What are the alternatives to kibana?

Grafana, OpenSearch Dashboards. Kibana's build failed after 1 second in our sandbox because its version check rejected Node v24.

Setup2/5Our source checkout installed but the build failed.Editor’s note: The source build rejected the observed Node version; installation in a supported runtime and a running service were not assessed.
Docs4/5The README has an install section (“Getting Started”) and a usage section (“Using a Kibana Release”); we did not run its quickstart ourselves.Editor’s note: The README gives product routes and compatibility rules; completeness and correctness of the linked operating instructions were not assessed.
Community4/5Last push on 2026-11-14, 21,377 stars and 14,867 open issues and pull requests is a heavy backlog for its size.Editor’s note: One current issue and the public release page establish activity, without assessing support responsiveness or adoption.
Maturity4/5Latest release v9.5.6 on 2026-11-02 and repository created 2013-01-26.Editor’s note: No running Kibana and Elasticsearch pair, migration or production workload was assessed in this source run.

How we score

Discussed on

  1. hnLicensing changes to Elasticsearch and Kibana298 points
  2. hnTelemetry settings in Kibana37 points
  3. hnOpen Source Flow Collecting with Elastic, Logstash, and Kibana11 points
  4. hnBuilding Real-Time Dashboards with Apache Flink, Elasticsearch, and Kibana6 points
  5. hnA New Architecture for Kibana5 points

Who it’s for

Teams already using Elasticsearch that want its companion data interface.
Operators able to coordinate Elasticsearch and Kibana versions.
Contributors prepared to use the exact runtime requested by a large source workspace.

Who it’s NOT for

Teams expecting a general interface for unrelated databases: the README defines Kibana around data in Elasticsearch.
Operators expecting unrestricted independent upgrades: the README marks an older Elasticsearch minor than Kibana as fatal.
Developers wanting a small charting dependency: our checkout contained 131,803 files and occupied 1,224.3 MB.
Redistributors assuming one permissive licence covers all code: the licence file makes coverage depend on source headers.

Setup reality

Our November 11, 2026 run at 650d1d3 completed installation in 52 seconds, recording 1 dependency and 2,423 MB on disk. The build failed with exit 1 after 1 second. The harness detected no test script or target and skipped tests; this isn't proof that Kibana has no tests.

Running Kibana usefully needs an Elasticsearch service with a compatible version and access configured for the intended deployment. The README recommends identical versions, explains allowed mismatches and points evaluators toward releases or Elastic's hosted service.

The log explicitly reports Node v24.19.0 and requests v24.22.1. The lab-node:22 image label doesn't establish that Node 22 ran. The recorded configuration was 3 CPUs and 8 GB RAM. No successful build with the requested runtime is recorded, and the single dependency field isn't a complete workspace package inventory.

Use Kibana when Elasticsearch is already your data platform

Kibana's source build stopped after 1 second in our sandbox because the running Node version didn't match the required version. That is a contributor-environment finding. For a team choosing a dashboard product, the more consequential requirement is Elasticsearch: Kibana's README defines it as the interface for querying, analyzing, visualizing and managing data stored there.

Choose it when that relationship is useful. A team already putting operational data into Elasticsearch has a clear reason to evaluate its companion interface. Someone seeking charts over unrelated databases should compare other tools before adopting a search cluster just to obtain the UI. Kibana's source checkout also deserves a separate decision from using a packaged release.

What happened when we ran it

Our November 11, 2026 run at 650d1d3 installed dependencies successfully in 52 seconds, then failed the build with exit 1 after 1 second.

Recorded step Result Duration
Install Succeeded; 1 dependency recorded; 2,423 MB on disk 52 seconds
Build Exit 1; rejected the running Node version 1 second
Tests No script or target detected by the harness; skipped Not run

The build command was node scripts/build --all-platforms. Its error says: Kibana does not support the current Node.js version v24.19.0. Please use Node.js v24.22.1. The sandbox image was labelled lab-node:22, yet this exact log establishes Node v24.19.0 for that command. The image label cannot override the observed runtime.

The supported next step is specific: use the requested runtime for the measured checkout and repeat the build. There is no measured result for that repeat. Calling Kibana's source code broken on this evidence would mistake a version check for a compilation failure.

The configuration specified 3 CPUs and 8 GB RAM. The checkout contained 131,803 files, approximately 15,186,208 source lines and 1,224.3 MB before the recorded installation footprint. The summary's single recorded dependency isn't a credible inventory of every package in this workspace repository. Keep the reported field, but don't turn it into a claim that Kibana has only one dependency.

The scan found 58 CI workflow files, monorepo workspaces, no Dockerfile and no tests directory. Those are scanner observations. In particular, the harness finding no test target doesn't mean the project has no tests.

Source development and trying the product are separate routes

The README points production users and evaluators toward downloadable releases or Elastic's hosted service. It describes local source work as a route for contributing code, exploring recent features or trying an open pull request. That distinction matters with a checkout exceeding a gigabyte before the recorded installation footprint.

For a product evaluation, I'd start with a release and a compatible Elasticsearch instance. Enter the source tree when you need to change Kibana itself. If source development is the job, pin the checkout and its requested runtime together before interpreting a failed command. Our build stopped early enough that it says little about the work remaining after that check.

Elasticsearch compatibility constrains the upgrade sequence

Kibana recommends running the same version number as Elasticsearch. The README allows Kibana to be ahead on patch versions or behind on minor versions, while warning that support will first request matching versions when troubleshooting a mismatch.

Its compatibility table marks an Elasticsearch minor older than Kibana as fatal, along with the illustrated major-version mismatches. The major-version rule also mentions an exception for prevmajor.last; don't replace that qualification with a blanket claim that every unequal version fails. For an operator, the useful action is to plan the pair's upgrade sequence against the documented relationships before upgrading either component independently.

A current issue shows why the missing test target needs careful wording

Issue #305485, opened November 14, reports an Entity ML anomaly-overview API check that expected HTTP 200 and received HTTP 502. It names a Scout/Playwright specification under the security solution and was open when read. That report is about a particular upstream check, separate from our Node-version rejection.

The release page lists Kibana 9.5.6 as the latest release when fetched. The recent release and new issue show ongoing release and tracking activity. They establish neither a clean local test run nor a support-response guarantee.

Grafana and OpenSearch Dashboards fit different data choices

Grafana documents mixing different data sources in the same graph. Evaluate it when your dashboard needs to span systems rather than center on Elasticsearch. That is a capability distinction, without a measured performance winner here.

OpenSearch Dashboards is designed to work with OpenSearch. If that is your search engine, start with its matching interface. Don't select Kibana on the assumption that all search backends are interchangeable.

Read the applicable licence headers before redistributing code

Kibana's licence file says coverage depends on the applicable source header. It describes a default AGPLv3-only, SSPL or Elastic License 2.0 choice, other Apache-compatible coverage, and code solely under Elastic License 2.0 in x-pack. A single permissive licence label would conceal those differences. Check the components and distribution you intend to use.

What we have not tested yet

This run didn't produce a build under the requested Node version or launch Kibana against Elasticsearch. Dashboard behavior, authentication, migrations and performance under real data volumes remain outside the evidence. Community research was not collected. Anonymous repository-facts and latest-release API requests returned HTTP 403, so fresh API counts and a last-push timestamp weren't established; the public release page remained readable.

All four ratings are unassessed: the rejected runtime doesn't support a setup-ease score, and reading the README and one issue doesn't establish documentation completeness, support quality or production maturity. For contributors, the next useful result is a build with the requested runtime. For adopters, it's a matching release pair answering a real question against your data.

Alternatives

ProjectWhat it isPick it when
Grafana gh↗A monitoring and observability interface with mixed data sources.Choose it when dashboards must combine queries from several data sources.
OpenSearch DashboardsA visualization interface designed for OpenSearch.Choose it when OpenSearch is the backend you intend to operate.

Sources

  1. Kibana README
  2. Kibana licence
  3. Kibana issue #305485
  4. Grafana README
  5. OpenSearch Dashboards README
  6. Kibana 9.5.6 release

More data reviews

Related reading