Lens visualization index pattern reference handling after index pattern rename in Kibana 8.x

Question

When an index pattern is renamed in Kibana Management > Index Patterns, Lens visualizations that reference the original pattern should continue to display data without manual intervention.

Currently, Lens visualizations retain the original index pattern identifier and require the user to open each visualization and update the index pattern reference manually after a rename. It is unclear whether a configuration option, space‑level permission, or saved‑object setting exists to enable automatic propagation of index pattern changes to Lens visualizations in Kibana 8.x.

Is there a supported configuration or setting that allows Lens visualizations to automatically follow index pattern renames?
If no such setting exists, what is the recommended approach to manage index pattern changes across many Lens visualizations without editing each one individually?
Are there any known limitations or side effects when attempting to automate index pattern updates for Lens visualizations via API or saved‑object manipulation?

Tasadduq Burney · Answer

Answer
No built‑in configuration or saved‑object flag exists in Kibana 8.x that makes Lens visualizations automatically follow an index‑pattern rename.
Why this happens
Lens visualizations store the index_pattern_id (the internal UUID) directly in their JSON. When you rename an index pattern only its title changes; the ID stays the same, but the UI shows the new name while the visualization still points to the original ID. Because the ID does not change on rename, the visualization continues to reference the old pattern unless you explicitly update the stored ID.
Steps to bulk‑update Lens visualizations

Identify the old index‑pattern ID (from Management → Index Patterns or via GET /api/index_patterns/_find).
Find all Lens saved objects that reference that ID:
GET /api/saved_objects/_find?type=visualization&fields=title,index_pattern_id&per_page=1000

For each returned object, replace the index_pattern_id value with the new pattern’s ID, keeping type, id, version and migrationVersion unchanged.
Send the updated objects in a bulk replace call:
POST /api/saved_objects/_bulk_replace
{
  "objects": [
    { "type":"visualization","id":"","version":,"migrationVersion":,"attributes":{ ...updated attributes... } },
    ...
  ]
}

Verify each visualization loads data without errors in the Lens UI.

Missing diagnostic detail
Do the old and new index patterns have exactly the same field list and data types? If they differ, visualizations may load but show empty data or errors even after the ID is updated; you would need to adjust the visualization or re‑create it.

Lens visualization index pattern reference handling after index pattern rename in Kibana 8.x

1 answer

Answer

Why this happens

Steps to bulk‑update Lens visualizations

Missing diagnostic detail

Your perspective belongs here.

0 question comments