E-Insights: After Migrating Insights Dashboards, the Corresponding Index Patterns Were Not Updated with the Target Database Suffix (Doc ID 3031978.1)

Last updated on JULY 01, 2024

Applies to:

Symptoms

After migrating custom Kibana Dashboards from one environment to another, when the custom indices are deployed in the target environment, what once was 'testindex_devdb' in the development environment, becomes 'testindex_tstdb' in the target environment. However, upon migration, the visualization that is imported into the target environment is not renamed. It remained kibana_test1_hdev, instead of being updated to kibana_test1_htst.

It was expected that the index pattern would follow the same naming standard and, in the example provided, be renamed to kibana_test1_htst. It instead remained kibana_test1_hdev.

The issue was reproducible in the customer site with the following steps:
1. Create custom Insights Dashboards.
2. Migrate the custom Insights Dashboards from the development environment to the test environment, following the instructions in Doc ID 2684543.1.
3. In the target environment, observe that the index patterns for the corresponding custom Kibana Dashboards have not been renamed with the correct database name in the suffix.

Example:
- index pattern in the source (development) environment: kibana_test1_hdev
- index pattern in the target (test) environment: kibana_test1_hdev => it was expected that the index patter, in the target environment, would be renamed to kibana_test1_htst, after the migration.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.