Metabase app Innovation Release
- Hybrid Manager dual release strategy
- Documentation for the current Long-term support release
Important
Regular upstream releases deliver security updates. Keep your Metabase instance up to date to receive the latest patches.
Metabase is a community-supported, open-source business intelligence tool available as an app in Hybrid Manager.
Key features
- Question builder that doesn't require SQL.
- SQL mode for ad hoc queries.
- Interactive visualizations and dashboards.
- Data exploration and automated analysis.
- Embeddable charts and dashboards.
- Support for multiple database backends (PostgreSQL, MySQL, and more).
Requirements
Supported data sources
For production, Metabase recommends using PostgreSQL as your Metabase application database:
- PostgreSQL (Primary), plus various SQL and NoSQL databases supported by the upstream Metabase image.
Before deploying, have your PostgreSQL database connection details ready (host, port, database name, username, and password). You can obtain these from the Connect tab of your cluster in the HM console. See Parameters for the full list of required and optional fields, including resource limits.
Deploying Metabase
Install Metabase directly in Hybrid Manager (HM).
- In the HM console, navigate to Asset Library, then select Apps.
- Select Metabase, select Deploy, and fill in the required fields. See Parameters for field descriptions.
Parameters
| Parameter | Description | Required |
|---|---|---|
PostgreSQL Host | Hostname or IP address of your PostgreSQL server. Examples: postgres.database.svc.cluster.local, prod-postgres.example.com, 10.0.1.50. | Yes |
Database Name | Name of the PostgreSQL database. Must exist on the PostgreSQL server. | Yes |
Database User Name | PostgreSQL user for the Metabase application. Must have access to the database. | Yes |
Database Password | PostgreSQL password for the database connection. | Yes |
PostgreSQL Port | Port number for the PostgreSQL connection. Default: 5432. | No |
CPU request | Requested CPU for the Metabase pod. Default: 500m. | No |
Memory request | Requested memory for the Metabase pod. Default: 1Gi. | No |
CPU limit | Maximum CPU for the Metabase pod. Default: 1000m. | No |
Memory limit | Maximum memory for the Metabase pod. Default: 2Gi. | No |
Note
Once you have deployed Metabase in HM, you can access it in the HM console under Apps or Asset Library.
Post-deployment configuration
Once Metabase is deployed, complete these steps to finish your setup:
- Navigate to your Project and select the Apps tab, or navigate to Estate > Apps to check the deployment status. When the status shows Ready, launch the app. A setup wizard guides you through the remaining configuration steps.
- Create an admin account in Metabase to manage all subsequent user additions, database connections, and system configuration.
- Choose between self-service analytics, analytics embedded in applications, or both. You can change this later.
- Provide your database hostname, port, name, and credentials. You can also skip this step and explore the sample database included with Metabase:
- Choose whether to allow anonymous usage data collection. Metabase never collects anything about your data or question results.
Support resources
As Metabase OSS is community-supported, use these resources for technical guidance and updates:
- Metabase discussion forum — peer-to-peer support from the community.
- Metabase documentation — self-service deployment and feature guides, as well as additional information on Metabase installation and configuration.
- Metabase GitHub repository — source code, issue tracker, and release notes.