If you are running the Mac OS X application on your laptop, you can click on the Help menu item and click
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 whoever it is that set up your company’s Metabase (a good starting point for this would be to ask whoever).
Our Mac OS X application is best thought of as Metabase in single-player mode. It’s meant to be a way to quickly try out the program 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.
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 currently supports:
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 is primarily meant to work with actual databases. However we have released a Google Analytics connector. We will be moving fairly slowly on this front however, ands suggest that you use other tools to build a data warehouse with the data you need. 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.
In the event of a clear bug, please open an issue.
If you’re having other 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.
Not yet. We’re working on it however, and you should expect it in the near future. (Late summer/early fall 2016). Keep tabs on it at the main tracking issue
We’re looking for operations engineers who can help our community deploy and run Metabase. You will primarily be responsbile for finding ways to make deploying Metabase to common platforms (AWS, GCE, Azure, Heroku, etc seamless. You will also be responsible for running our internal platforms.
Metabase is looking for a Lead Front-end Engineer, who will be responsible for our front-end codebase across our suite of analytics applications. You will own the build, test and deployment of our front-end clients as well as writing code, mentoring and help us grow our engineering team. Strong product sensibilities are expected as you’ll have a significant part in shaping our user experience.
Metabase Product Advocates are our main point of contact with our user community. As a product advocate, you’ll engage with our users one-on-one, but a large part of being an advocate at Metabase is looking for ways to make sure that each time someone encounters an issue the whole community benefits from the solution. You’ll act as our eyes and ears and let us know what users are confused by, help us determine what should be added to the product and relay information from our user community. You’ll also write blog posts, scripts and other educational material so that the whole Metabase community can learn from what you discover.
Metabase needs someone to wrangle all of our user facing documentation and educational content. Day to day, you’ll be a force for simplicity and clarity - collecting information from product managers, support and engineering, and turning it into something people can actually understand. You’ll own the organization of our documentation, faqs and other educational resources.