ML
Kibana

Discover, Lens, TSVB: Which Kibana Visualisation Should You Use?

Kibana ships three overlapping editors. The differences matter — pick wrong and you hit a ceiling three weeks in.

July 05, 20257 min readKibanaDashboards

New Kibana users often make the same mistake: they open whatever visualisation editor they opened first, and they stay there. Discover, Lens, and TSVB are optimised for different work.

Discover — raw document exploration

The home of ad-hoc investigation. You're reading actual documents, filtering with KQL, and saving searches — not drawing charts. Discover is where you figure out what your data actually looks like before you visualise anything.

service.name : "payments-api" and http.response.status_code : 500
  and @timestamp >= now-1h

Lens — the default for most dashboards

Drag-and-drop with smart suggestions. It produces proper bucket/metric aggregations under the hood and exports clean JSON. Limitations:

  • No pipeline aggregations (cumulative sum, moving avg) out of the box.
  • Series-level expressions are constrained — one formula per layer.

Lens is what to use when a teammate will maintain the dashboard.

TSVB — the power tool for time-series

Time Series Visual Builder exposes the full aggregation pipeline: math, moving averages, rate-of-change, series filters. It's the right choice when you need:

  • Percentile bands (p50/p95/p99 on one chart).
  • Ratios between two queries: errors / requests.
  • Split-by-term with a secondary filter per series.

The honest trade-off

TSVB dashboards are harder to hand off. Expressions encode behaviour in a small DSL that your teammates may or may not read. A practical rule: reach for Lens first, switch to TSVB only when you hit a real wall.

And: Vega

If you need a chart Kibana simply can't draw — a Sankey, a chord diagram, a custom map overlay — Vega-Lite is the escape hatch. It talks to Elasticsearch directly via data.url.%context%. Write very few of these; they're the first to rot on upgrade.

SharePostLinkedIn

Reader Discussion

6 replies// weighed in

TopNewestAuthor
Add to the thread
Disagree, agree harder, or share your own experience…
Email instead →markdown okbe kind
  1. Hannah Kaur· Product EngAgrees

    tbh TSVB is powerful but the learning curve filters out non-SREs. Lens is the right default for cross-team dashboards in 2026. Hot take: TSVB should have been deprecated by now.

    Jul 11, 2025·6 days later·edited
  2. Rodrigo Alves· Data AnalystFrom experience

    the KQL/Lucene gotcha on analyzed fields has bitten me 5+ times. status: "Active" returning zero hits because the field is text-analyzed and lowercased to "active". it's not a bug, it's a foundational pain.

    Jul 10, 2025·5 days later
  3. Fatima Al-Zahra· Security EngineerStory

    DLS/FLS is so under-rated. We were 3 sprints into building a custom tenancy proxy when someone surfaced these features in a brown bag. Cancelled the project. Saved an entire quarter of work.

    Jul 09, 2025·4 days later
  4. Takeshi Mori· PlatformAgrees

    the 'space membership + role + ES privilege' three-way alignment is the source of every "why does this dashboard return zero hits" ticket I've ever closed. should be a chart in onboarding.

    Jul 10, 2025·5 days later
  5. Evi Papadopoulou· Tech LeadFrom experience

    canvas is great until someone makes a 47-element dashboard and the page hangs for 8s. happy mediums exist somewhere between "4 KPI tiles" and "art project". still love it for exec readouts though.

    Jul 11, 2025·6 days later
  6. Rachel Gold· Staff SREAgrees

    the on-call framing throughout this piece is what makes it land. too many infra articles assume you never get paged. those are written by people who never got paged.

    Jul 08, 2025·3 days later

Worked on something similar? Email ducminhldm@gmail.com — I read every one. The good ones become future posts.

Comments seeded · live discussion via email