Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Cloud Search Service/ Best Practices/ Elasticsearch Data Migration/ Migrating Kibana Saved Objects Between Elasticsearch Clusters

Migrating Kibana Saved Objects Between Elasticsearch Clusters

Updated on 2025-01-06 GMT+08:00

Scenarios

You may want to migrate Kibana's saved objects between Elasticsearch clusters in the following scenarios:

  • Data migration: When migrating data from one Elasticsearch cluster to another, migrating Kibana's saved objects is a key step to ensure service continuity. Exporting Kibana's saved objects (such as visualizations and dashboards) from the source cluster and importing them to the destination cluster ensures consistency in the user interface and monitoring dashboards.
  • Environment replication: When replicating an Elasticsearch environment between the development, testing, and production environments, migrating Kibana's saved objects ensures consistency across different environments, thus improving development and testing efficiency.
  • Service failure or data loss: In the event of a service failure or data loss, migrating Kibana's saved objects to a backup cluster helps to quickly restore data monitoring and analytics capabilities.
  • Multi-cluster management: In a multi-cluster environment, consolidating data and other objects from different Elasticsearch clusters into a single cluster enables cross-cluster data analysis and management.

These scenarios highlight the importance of migrating Kibana's saved objects between Elasticsearch clusters. It is not just about the movement of data; it's a crucial method to ensure service continuity, improve efficiency, and guarantee compliance.

Solution Architecture

Figure 1 Migrating Kibana saved objects between Elasticsearch clusters

Figure 1 illustrates the process of migrating Kibana's saved objects between Elasticsearch clusters.

  • The first step is exporting Kibana's saved objects from the source Elasticsearch cluster.
  • The second step is importing these objects in the destination Elasticsearch cluster.

Advantages

  • Service continuity: During a cluster upgrade or migration, migrating Kibana's saved objects ensures the continuity of cluster monitoring and analytics tasks.
  • Cross-environment consistency: Replicating Kibana's saved objects across different environments (development, testing, and production) helps ensure environment consistency, improving development and testing efficiency.
  • Quick recovery: In a fault recovery scenario, migrating Kibana's saved objects helps quickly restore cluster monitoring and analytics capabilities, mitigating the impact of any downtime.
  • Data consolidation: In a multi-cluster environment, consolidating the data from different clusters by migrating Kibana's saved objects enables centralized data management and analysis.

Constraints

To avoid migration errors or failures, the versions of the source and destination Elasticsearch clusters must be close. If a version incompatibility error occurs during migration, handle it by referring to FAQ: How Do I Handle a Version Incompatibility Error Reported During the Migration of Kibana's Saved Objects?.

Prerequisites

The source and destination Elasticsearch clusters are available.

Procedure

NOTE:

The Kibana UI may vary depending on the Kibana version. The following uses version 7.10.2 as an example.

  1. Export Kibana's saved objects from the source Elasticsearch cluster to a local PC. In our example, the source cluster is an Elasticsearch cluster on Huawei Cloud.

    1. Log in to the CSS management console.
    2. In the navigation pane on the left, choose Clusters > Elasticsearch.
    3. In the Elasticsearch cluster list, locate the source cluster, and click Access Kibana in the Operation column to log in to the Kibana console.
    4. In the navigation tree on the left, choose Stack Management > Saved Objects.
    5. On the Saved Objects page, click Export xx objects. In the displayed dialog box, select the types of objects you want to export, and click Export all. An export.ndjson file is exported to the local PC.
      Figure 2 Exporting Kibana objects

  2. Import Kibana's saved objects exported in the previous step to the destination Elasticsearch cluster.

    1. On the CSS management console, choose Clusters > Elasticsearch.
    2. In the Elasticsearch cluster list, locate the destination cluster, and click Access Kibana in the Operation column to log in to the Kibana console.
    3. In the navigation tree on the left, choose Stack Management > Saved Objects.
    4. On the Saved Objects page, click Import. In the displayed dialog box, select the source cluster's export.ndjson file saved on the local PC. Select Automatically overwrite conflicts for Import options, and click Import.
      Figure 3 Importing Kibana objects
    5. Click Done when the import is finished.

FAQ: How Do I Handle a Version Incompatibility Error Reported During the Migration of Kibana's Saved Objects?

If the following error message is displayed when you import Kibana's saved objects, the source and destination clusters have incompatibility issues.

The file could not be processed due to error: "Unprocessable Entity: Document "7.1.1" has property "config" which belongs to a more recent version of Kibana [7.13.0]. The last known version is [7.9.0]"

In this case, you can modify the version information in the export.ndjson file on the local PC to keep the versions consistent. In this example, you need to change [7.13.0] to [7.9.0] in the code. Then, save the change and import the file again. If the import still fails, you will have to manually rebuild the objects in the destination cluster.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback