If you are running the MacOS application on your laptop, you can click on the Help menu item and click Reset Password.
If you are using a browser to access Metabase, then someone downloaded our software and installed it on a server. We at Metabase don't host your instance. We write software that someone at your company decided to run. You should ask whomever it was that set up your company's Metabase for help resetting your password.
Our macOS application is best thought of as Metabase in single-player mode. It's meant to be a way to quickly try Metabase out and see if it's something you'd want to use across your team. It's also useful for use on your own.
When you need to share dashboards or pulses with others, we strongly recommend you run our server application.
Yes.
Metabase does not expose a "Join" operator, but we do provide ways for non-SQL-proficient users to perform the tasks that joins are used for such as filtering or grouping by columns in other tables, etc.
For more info see our blog post on the subject
The primary audience of the GUI querying interface is a non-technical user who doesn't SQL. Advanced users can always use SQL.
We're constantly trying to walk the line between putting more functionality into the GUI interface and creating a confusing mess. You can expect it to improve and change with time, but in the meantime, you can always lean on SQL directly for the complicated matters.
Metabase allows you to click on your charts or tables to explore or zoom in, but these features don't currently work with SQL/native queries (this is because Metabase doesn't currently parse these kinds of queries). The same is true of the question actions menu in the bottom-right of the question detail page.
However, in Metabase version 0.25 we introduced nested queries, a feature that lets you use the results of SQL/native queries as the starting table for GUI-based questions. This means you'll be able to use sophisticated SQL/native queries to create the exact segments you need, and you and your team will be able to use drill-through and actions if you create GUI-based questions from those segments.
By default, Metabase attempts to make field names more readable by changing things like somehorriblename to Some Horrible Name. This does not work well for languages other than English, or for fields that have lots of abbreviations or codes in them. If you'd like to turn this setting off, you can do so from the Admin Panel under Settings > General > Friendly Table and Field Names.
To manually fix field or table names if they still look wrong, you can go to the Metadata section of the Admin Panel, select the database that contains the table or field you want to edit, select the table, and then edit the name(s) in the input boxes that appear.
Not currently, but these are all enhancements that we're considering.
When one or more dashboard filters are active, any card on that dashboard that isn't connected to every currently active filter will fade out a bit to clarify that they are not being affected by all active filters. We understand this behavior is contentious, so we're actively discussing it on GitHub.
Not directly. But if a user does not have permission to view any of the cards that a dashboard includes, she won't see that dashboard listed in the Dashboards section, and won't be allowed to see that dashboard if given a direct link to it. Additionally, we're currently actively considering placing dashboards inside collections, which would allow administrators to use collection permissions to restrict user group access to dashboards the same way they currently can to restrict access to saved questions.
Metabase has minimum size limits for dashboard cards to ensure that numbers and charts on dashboards are legible. You might be asking this question because you're trying to fit a lot of things in a dashboard, and another way we're exploring to solve that problem is by making it easier to put more than one series or metric in the same question, which would reduce the number of cards required to be on a dashboard in the first place.
In an effort to make sure that dashboards are legible, Metabase changes the way charts and numbers in cards look at different sizes. When a number card is small, Metabase abbreviates numbers like 42,177 to 42k, for example.
Metabase automatically changes the visualization type of saved questions you put in Pulses so that they fit better in emails and Slack. Here is an inventory of how charts get changed, and here is the logic for how this works.
We understand this behavior isn't expected, and are currently exploring ways to handle this better.
Metabase currently has a limit on how many columns and rows can be included in a Pulse as a safeguard against massive tables getting plopped in users' inboxes, but this is an issue we're actively discussing changing.
Not yet, but the community is working on it!
Not yet, but we'd love your help working on implementing designs for this feature.
No, this is currently a limitation with the way we're required to implement our Slack integration.
Metabase currently supports:
- Amazon Redshift
- BigQuery
- CrateDB (version 0.57 or higher)
- Druid
- H2
- MongoDB (version 3.0 or higher)
- MySQL (and MariaDB)
- PostgreSQL
- Presto
- SQL Server
- SQLite
Metabase is built by a small core team, and we have very limited engineering bandwidth. Each additional database we connect to slows down overall product development, increases the time and cost of our automated testing and requires us to learn a lot about the edge cases of the specific database driver. While writing a given driver might only take a few days, supporting it places a cost on us indefinitely.
That said, we will build out additional database connectors as we are able to. We generally select additional drivers based on demand from the community and our ability to set up a test database server easily in our integrated testing environment.
We welcome community contributions of database connectors. If you're able to help, we have open issues for a number of databases. We'd greatly appreciate your help!
Metabase currently supports Google Analytics as a data source. The connection can be set up by an admin the same way database connections are set. If you are using Google Analytics Premium, one of the features is direct access to a BigQuery database with your personal Google Analytics data. BigQuery is also supported by Metabase.
We do not currently offer a way to connect to other third-party APIs or services directly. What people do instead in these situations is download data from these services into a database they control and then use Metabase to access that database directly. This can be done either by writing code or more commonly using a third-party service. There are a large number of these services, and you can ask other users and discuss pros and cons at our user forum.
Not exactly. Metabase provides access to data you have in an existing database you control. We currently do not add or modify the information in your database. You should ask whomever controls the database you are accessing how to upload the data you're interested in accessing.
Yes, to the extent that we are able to and have time.
If you're sure you've found a bug, please open an issue. Otherwise, try checking out the troubleshooting guide first to see if the answer to your problem is there.
If you're still having trouble, please start a conversation at our discussion forum and check out the other threads. Someone else might have experienced the same problem.
We are experimenting with offering paid support to a limited number of companies. Contact us if you want more information.
Yes, Metabase offers two solutions for sharing charts and dashboards:
- Public links let you share or embed charts with simplicity.
- A powerful application embedding let you to embed and customize charts in your own web applications.