Kibana Maps and Canvas

1. Kibana Maps #

Visualising geography.

Geographic data #

Maps reads geo_point (a position) and geo_shape (a shape) fields. They come from the Logstash geoip filter, the geoip processor of an ingest pipeline, or directly from the application.

PUT _ingest/pipeline/geo-web
{ "processors": [ { "geoip": { "field": "source.ip", "target_field": "source.geo" } } ] }

PUT magasins
{ "mappings": { "properties": { "position": { "type": "geo_point" }, "zone": { "type": "geo_shape" } } } }

Layers #

Good practice: Beyond a few thousand points, switch to a cluster or grid layer: the map stays readable and fast.

Good to know: A map is added to a dashboard like any other panel and follows its filters and time range.

2. Canvas #

Live presentations.

Principle #

Canvas builds workpads (free-form, pixel-precise pages) from elements: metrics, charts, images, Markdown text. Each element queries live data, often in Elasticsearch SQL, and can be styled with CSS: ideal for a wall screen or a branded report.

filters
| essql query="SELECT \"geo.src\" AS pays, COUNT(*) AS requetes FROM \"kibana_sample_data_logs\" GROUP BY pays ORDER BY requetes DESC LIMIT 5"
| pointseries x="pays" y="requetes"
| plot defaultStyle={seriesStyle bars=0.75 horizontalBars=true}
| render

Depending on the version: Canvas evolves little compared with dashboards and Lens, which cover most needs; keep it for bespoke layouts.

3. Sharing and exporting #

Links, embedding, reports.

Options #

• Shared link (with a fixed or relative time range) and iframe embedding.
• CSV export from Discover and tables.
• PDF and PNG reports of dashboards and workpads, optionally scheduled.

Good to know: PDF and PNG reports depend on the licence (paid subscription or trial); CSV export is available with the Basic licence.