Dump the data from the origin environment.Create dashboards and collections in the origin environment.Spin up two instances of Metabase: origin and target.Create a dedicated network called metanet.You can even put the dump files into version control and audit changes to them, as the YAML files contained within the dump are pretty readable.Ĭurrently, it has a dump feature on Collections, Dashboards, Saved questions, Pulses, Segments and Metrics defined in the Data Model, Archived collections, dashboards, saved questions, or pulses, Public sharing settings for questions and dashboards, Admin Panel settings, except for permissions, Database connection settings, Data Model settings.īut it can be available only on Enterprise Edition in Metabase.įollow these steps to implement the above: You could also use this feature to enable a staging-to-production workflow for important dashboards or reports by dumping from a staging instance of Metabase and then loading that dump into your production instance(s). This lets you do things like create a set of dashboards and charts in one Metabase instance and then easily copy those items to a number of other Metabase instances. Metabase has a serialization feature that lets you create a snapshot, called a dump, of the contents of a Metabase instance that can then be loaded into another instance. Use the Serialization feature- ENTERPRISE VERSION ONLY!! Use dump data for migrationĪ very simple solution to this problem is creating a script to dump data of one instance with all data like dashboards, collections, cards or questions, etc., push it to s3, and again have another script to import this dump data in another Metabase instance.īut the problem with this solution is that it dumps all the data from one instance to another instance means we can not customize our solution and it becomes complicated to integrate it with CI/CD pipeline, as for every deployment we would need to use Metabase REST APIs for updating any passwords for the “Connected Databases”, as it might differ on different instances. There are three most useful possible solutions for importing and exporting contents of one Metabase instance to another. So, what can we do in these cases when we need Metabase dashboards and questions to be replicated in multiple environments? Solutions We might have a couple of testing or development instances and a production one. Once we really get rolling with Metabase it’s often the case that we will have more than one instance of it spun up, especially when we want to embed or display our Dashboards and Questions in a Client Application. Importing and Exporting Dashboards Need for import and export contents It has an active community on GitHub, the documentation is very complete, and is possible to connect with several databases (BigQuery, Druid, Google Analytics, H2, MongoDB, MySQL, PostgreSQL, Presto, Amazon Redshift, Snowflake, Spark SQL, SQLite, SQL Server). Metabase also makes it easy to share questions and dashboards with the rest of your team. Your questions can be saved for later, making it easy to come back to them, or you can group questions into great-looking dashboards. It lets you ask questions about your data, and displays answers in formats that make sense, whether that’s a bar graph or a detailed table. Metabase is an open-source business intelligence tool. First of all, let’s talk a bit about Metabase.
0 Comments
Leave a Reply. |