Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators Community. The Global Innovators Community is an ...

Metabase Q Joins World Economic Forum Global Innovators Community

Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators Community. T

SAN FRANCISCO--(BUSINESS WIRE)--Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators Community. The Global ...

SAN FRANCISCO–(BUSINESS WIRE)–#ATM–Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators Community. The Global Innovators Community is an invitation-only group of ...

MotherDuck, builder of the serverless, easy-to-use data analytics platform based on open source database DuckDB, is announcing the results of its Series B funding round, accumulating a total of $52.5 million and bringing its total funding to date to $100 million.

MotherDuck Raises $52.5M in Series B Funding

Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators Community. The Global Innovators Community is an invitation-only group of the world’s most promising start-ups and ...

SAN FRANCISCO–(BUSINESS WIRE)–September 22, 2023– Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum’s (WEF) Global Innovators ...

Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum's (WEF) Global Innovators Community. The Global Innovators Community is an invitation-only group of the world's most promising start-ups and ...

Metabase Q, a leading all-in-one cybersecurity solution, today announced it has joined the World Economic Forum's (WEF) Global Innovators Community. The Global Innovators Community is an ...

Metabase

metabase

Metabase & Substrate: A Simple and Flexible, Yet Unscalable, Approach to Data Analysis

“Data is the new oil”. We have all heard this adage but does it fit in the startup ecosystem? The statement might be true for large enterprises which have multiple verticals and many departments looking at metadata or transactional level information to make sense of it, but what about a growing startup? Is Metabase the answer? It’s wise to start early and bloom according to the customer or market requirements when they come. As mentioned earlier, large enterprises might have data engineers setting up pipelines, and dedicated personnel preparing dashboards and presentations using the data collated from the multiple divisions of the organization, but a startup has limited resources in terms of man-hours and funds. This is where our trusty friend Metabase comes in. Metabase is a business intelligence tool that lets you access your data in a read-only manner. The only setup required is getting the docker up and running, then following the steps to add your database. No engineers or extra licensing costs are involved. Let’s dig deeper (for the “oil”) We at Decentro have a central RDBMS database containing transactional data. This makes querying the data easier and extracting information a piece of cake. Metabase sits on a separate instance and has read-only access to this database. Components of Metabase Metabase has 4 important components – – Written and saved queries that can be altered using the query editor or the custom question (used to visually provide filters and grouping options) Questions – A set of questions makes a collection. This binding of questions makes them easily manageable. Collections – The users of Metabase. People – Collections, but for people Groups Metabase allows to be self-onboarded using Google SSO which works very well for us at Decentro. Once a person is onboarded we assign them a , and the group in turn defines the accesses to the tables and that they will have. The permissions can be to simply view in a collection or curate them as well. Groups have policies to manage the access to collections and questions which are managed by the admins very stringently. people group collections questions Based on this framework, we have internally divided people into 3 groups Operations and Sales Product Developers team requires access to dashboards and questions that deal with customer success. Issues like Success rate dipping below a certain threshold, transaction-related issues, and customer billing. Similarly, the Sales team can check how their clients are doing using the data from Metabase. The Operations team needs to have a look at turnaround times, success metrics, and data anomalies. All of these fit in very well with the Metabase way of doing business. It helps the team to preemptively check for issues or inefficiencies in the APIs that our customers use. The Product are provided access to Metabase when they are working with the operations team to debug issues on production servers or to do configuration checks or root cause and corrective analyses (RCCA). Since developers work with SQL day in and day out, they can write queries to solve these problems and have a window to the production database. Developers As you can see the efficiency of the whole Decentro team is benefitted from Metabase. Why is Metabase awesome? Now that we have seen how to tap into efficiency, let’s deep dive into the why. Visualizations. Boom. Just, effortless visualizations. I just fetched some information from the database but I want to make a graph with it. Scenario: : A few clicks in the visualization tab and it’s done. Solution No pesky configuration options. Just a clean interface. Let’s take a closer look at a real-time scenario for better visualization. Below I have a query to fetch Transactions per second for one of the servers. This data represents the traffic on that server and is originally received in tabular format. But tables are not very intuitive. However, charts are. So I click on the visualization tab and switch my mode from data to visualization, and voila! Bar graph Now, this looks cool and intuitive. I have chosen a bar graph to analyze the TPS data more efficiently. But what if I wanted to further customize it to my liking? There are options such as setting a goal line if you want to set targets, changing colors (not shown in the screenshot below), showing a trend line, and many more, for each chart type. All the customization is focused on incorporating efficiency, and a level of intuitiveness with each chart. Stacking option Axes configuration Final Visualisation As you can see, my chart now looks good enough for our team to consume, and infer information from. Conclusion Metabase is a very important tool in the arsenal of a growing startup. Its impact might be low in the beginning, but as time passes on it becomes more and more valuable. Data-driven product and engineering decisions are what empower Decentro to understand customer pain points and work on them without the customers conveying them verbally, and Metabase is the silent aid for such decisions. In case it spikes your interest, our engineering team at Decentro has penned more tech blogs to satisfy the developer within you. Be it why we moved to , or a pocket guide on . Kong API Gateway from NGINX API Request Validation We’ll see you next time with yet another tech story! Also published . here

How to Build a Data-Driven Product Using Metabase

In the " " story, I describe the approach enhancing your debugging possibilities. On the one hand, I decided that adding description would add misleading details to the narrative. On the other hand, real-life applying might be an excellent opportunity to demonstrate method flexibility. 3 Sharpest Instruments for Debugging a meticulous coding This contradiction led to emerging of this auxiliary story. What Is Going on? On GitHub, there is a project called . I discovered it by searching through the trending repositories. I narrowed down my search by filtering to only those repositories that use the Clojure language I like. My specialization is mostly front-end, so I've chosen that might not be of considerable interest to other developers. I acted so as not to discover that someone passed over me with fixing it. After some investigation described in the primary article about fixing, I found out that the bug exists in the component. Metabase UI issue #14782 AccordionList Diving Into the Details Here's how the initial checklist would look: 1. Understand the actions required to implement task #14782
2. Write the commit messages for task #14782
3. Create a branch for task #14782
4.
5. Verify the correspondence of the implemented solution to task #14782
6. Create task #14782 PR
7. Pass the review of task #14782
8. Merge task #14782 into `master` In , there were 11 steps in the checklist. We do not need three of the administrative tasks, so I removed them. Also, I rewrote the last one to reflect the aspects of the situation. the original article about meticulous coding Let's act on the first task here and understand what do we need to do: 2. ...
3. Create a branch for task #14782
4. Prevent `AccordionList` from jumping on inner search value change task #14782
5. Verify the correspondence of the implemented solution to task #14782
6. ... The second task asks to write the commit messages. I didn't find any recommendations about the formatting of commit messages, so here is mine: Prevent Saved Questions search input from jumping The third task is about creating the branch. I also didn't find any recommendations on branch naming, so here we go: fix/14782-prevent-saved-questions-search-input-from-jumping Now it's time to solve the problem. The full description of discovery and solution is in the dedicated "Three Sharpest Instruments on Your Debugging Service" story. While trying to prepare the necessary state of the component, I discovered that the problem might no longer exist. I need to verify this. AccordionList 3. ...
4. Ask if task #14782 is still relevant after the "Add saved questions picker" update
5. Wait for someone's reply to my question about the relevance of task #14782
6. Prevent `AccordionList` from jumping on inner search value change task #14782
7. Verify the correspondence of the implemented solution to task #14782
8. ... I've shifted all the undone tasks by adding two on the fourth position. The fifth might sound unusual. I learned such a type of task by reading " " by David Allen. You set something reminding you about liabilities others have taken. By doing so, you clearly state the next step of the process and know the action required to unblock it. Or at least to try doing so. Getting Things Done It turned out that, indeed removed the problem I was tackling. As I mentioned before, the meticulous coding method is flexible. We delete all the tasks from the sixth, add another verificatory one and end up with the following completed checklist: the PR #16808 ☑ Understand the actions required to implement task #14782
☑ Write the commit messages for task #14782
☑ Create a branch for task #14782
☑ Ask if task #14782 is still relevant after the "Add saved questions picker" update
☑ Wait for someone's reply to my question about the relevance of task #14782
☑ Ensure the closing of task #14782 Thank you for reading! Please reach out if you want to discuss the ideas I describe. on Twitter

The Meticulous Coding Strategy Applied to Metabase Issue #14782

Metabase is a business intelligence tool for your organisation that plugs in various data-sources so you can explore data and build dashboards. I'll aim to provide a series of articles on provisioning and building this out for your organisation.  This article is about getting up and running quickly. There are multiple ways to get Metabase up and running on Google Cloud. https://www.metabase.com/docs/latest/operations-guide/installing-metabase.html You can install it locally on your Mac as well as popular cloud platforms. It's available as a JAR file and also as a Docker container. I went via the Docker container route and Google Cloud Platform. Step 1 - GCloud Developer Tools Setup Make sure you have GCloud developer tools setup. You can do this via the instructions . here After that, you'll need to login to your Google account and also configure Docker to work with your credentials.  In my case I generated a new service account in GCP to access Google BigQuery (my chosen reporting database).  I then downloaded the corresponding service account JSON file. gcloud auth login gcloud auth configure-docker Step 2 - Deploying Metabase to GCP Metabase docker images are on Dockerhub here. https://hub.docker.com/r/metabase/metabase/tags However, I wanted these in Google Cloud Registry for performance and reliability reasons. You can pull the Docker image using the following: docker pull metabase/metabase:latest Tag the docker image with the following: hostname — eu.gcr.io projectname — krustysfunhouse tag — metabase docker tag metabase/metabase:latest eu.gcr.io/krustysfunhouse/metabase Deploy the Docker image to Google Cloud Registry with the following docker push eu.gcr.io/krustysfunhouse/metabase:latest Step 3 - Compute Engine Instance Create a Compute Engine instance: - Specify the GCR image you've just uploaded: eu.gcr.io/krustysfunhouse/metabase:latest Specify vCPU and Memory (I used 1 vCPU and 3.75GB) Specify the region, I've used London (europe-west2-c) here. n.b. You'll have a by default. container optimized OS Step 4 - Getting Access Once that instance is provisioned you can login from gcloud via the console with the following: gcloud beta compute ssh --zone "europe-west2-c" "metabasereporting" --project "krustysfunhouse" Metabase runs as a Java app and starts-up on port 3000. If you want to get into installing Nginx or GCP Load Balancing that’s a different story. For this, I opened up access to port 3000. Add a new Firewall Rule to allow traffic to access tcp:3000 for now — example below. Then add this “name” to the machine VM instance as a network tag. You should lock this down to your office IP ideally, or setup a VPN so that you access this securely.  Once running, you will have a publically accessible instance that is subject to brute-force attack in terms of username/password. By default, Metabase will make you specify a default email and password, but still this isn't production ready. I'll look at the basics of building a dashboard in the next article, but hopefully that should be good enough to get you started. I'm a Consulting CTO working as an architect and engineer with startups and scaleups.  A large part of my career was spent working in analytics companies and data-heavy companies often with the aim of building/transforming data-platforms.  You can find out more about me (and hire me for advice, fractional or interim work) here: https://www.hwintegral.com/ That's all for now...

Stories, News & Mentions about METABASE

Metabase’s Stories on HackerNoon

Metabase's News & Mentions