4 ms·

Would be useful to have some information how this compares with https://www.metabase.com/ https://www.metabase.com/ or https://meltano.com/ https://meltano.com/

by cateye 7y ago

WrtCdEvrydy 7y ago
Metabase can't be beaten in terms of looks and functionality but I do like this.
- massaman_yams 7y ago
  Superset's not the best in terms of looks, but it beats Metabase hands down for functionality.
  - polskibus 7y ago
    Which functionalities would you point out as the most important in Superset that are missing in Metabase?
    - massaman_yams 7y ago
      Depends heavily on your use case, but there are a lot of advanced features. From a review last year (so some of this may be outdated): - Broader datasource support - 20 sources in Superset, vs 12 in Metabase Superset supports: - view creation by users ('create table as'), as well as materialization - geo/GIS based visualizations - day over day, week over week, etc. charting; moving averages, etc. Superset is missing data catalog-like functions, which metabase has, though I didn't evaluate metabase's data catalog in depth. It also requires you to write SQL, where Metabase includes a query builder UI - though there was a rather strange difference in capabilities within Metabase between the SQL-based charting and the query builder UI.
- roelb 7y ago
  Don't agree, in the past metabase was good, now it's just getting worse. I was a big fan of metabase (to the point I deployed it in 4 companies and rolled it out for many people to use in their daily workflow). All was nice. Somewhere around 0.31 something changed in the internal dev/release flow. I get the feeling they have some kind of internal push to add unnecessary untested features which all look nice on paper, and work on a 5-row 5-column user tables. Until you actually use those features and all functionality fails miserably.. Had weird issues with it, which usually occurred after upgrades, on both small and bigger decently indexed DB's (pg and mysql), things like: - had sets of reports which all worked fine until they hit a 1001 rows.. and suddenly the UI had a react race condition. - X-Rays which silently fail and break the UI, while on the DB server you see the queries complete. - Deployed new versions which would hammer databases by distincting every column individually every hour, instead of handling statistics a bit more intelligently. Disabled that ofcourse. - Deployed versions in other countries, where the UI client-server latency caused the whole UI to break (probably the limits of setTimeout reached? :-)). If you check the github issues, it's just ignored problems and they are focus on releasing new functionality instead of fixing the issues. Doesn't really motivate to report anymore problems. They had one good thing: they would allow you to work in sql and write efficient queries, but clearly they decided it's time to remove the last good feature and now only want graphical query builders. If you use metabase: deploy it on a replica such it doesn't whack your prod DB. And take backups before upgrading, because there is no revert. I've spent enough time on Metabase problems, won't touch it anymore.
  - salsakran 7y ago
    I'm on the Metabase team - We've walked a fine line between fixing bugs, adding the features that our users have asked for and building out the BI interface we think the world should be using in 5 years. We don't always get it right, and I'm sorry if we broke things for you on the performance side. We will be spending a few of our development cycles after 0.33 to try to clear out our bug queue. One specific factual point I'd like to reply to however - SQL isn't going anywhere. If anything we're making it easier to both write plain SQL, use SQL templates or use our graphical interface on top of SQL query results in our next release (preview at https://github.com/metabase/metabase/releases/tag/v0.33.0-preview2 https://github.com/metabase/metabase/releases/tag/v0.33.0-pr...)
- westpfelia 7y ago
  Is there anyway to use a BI tool like Metabase and combine it with Qradar? I'm interested in being able to create useful reports.
tdhz77 7y ago
I’m still using informixDB so the bring your own jbdc connector maybe what I was looking for in Poli.

Would be useful to have some information how this compares with https://www.metabase.com/ https://www.metabase.com/ or https://meltano.com/ https://meltano.com/

by cateye 7y ago

Would be useful to have some information how this compares with https://www.metabase.com/ https://www.metabase.com/ or https://meltano.com/ https://meltano.com/

WrtCdEvrydy 7y ago

Metabase can't be beaten in terms of looks and functionality but I do like this.

massaman_yams 7y ago
Superset's not the best in terms of looks, but it beats Metabase hands down for functionality.
- polskibus 7y ago
  Which functionalities would you point out as the most important in Superset that are missing in Metabase?
  - massaman_yams 7y ago
    Depends heavily on your use case, but there are a lot of advanced features. From a review last year (so some of this may be outdated): - Broader datasource support - 20 sources in Superset, vs 12 in Metabase Superset supports: - view creation by users ('create table as'), as well as materialization - geo/GIS based visualizations - day over day, week over week, etc. charting; moving averages, etc. Superset is missing data catalog-like functions, which metabase has, though I didn't evaluate metabase's data catalog in depth. It also requires you to write SQL, where Metabase includes a query builder UI - though there was a rather strange difference in capabilities within Metabase between the SQL-based charting and the query builder UI.
roelb 7y ago
Don't agree, in the past metabase was good, now it's just getting worse. I was a big fan of metabase (to the point I deployed it in 4 companies and rolled it out for many people to use in their daily workflow). All was nice. Somewhere around 0.31 something changed in the internal dev/release flow. I get the feeling they have some kind of internal push to add unnecessary untested features which all look nice on paper, and work on a 5-row 5-column user tables. Until you actually use those features and all functionality fails miserably.. Had weird issues with it, which usually occurred after upgrades, on both small and bigger decently indexed DB's (pg and mysql), things like: - had sets of reports which all worked fine until they hit a 1001 rows.. and suddenly the UI had a react race condition. - X-Rays which silently fail and break the UI, while on the DB server you see the queries complete. - Deployed new versions which would hammer databases by distincting every column individually every hour, instead of handling statistics a bit more intelligently. Disabled that ofcourse. - Deployed versions in other countries, where the UI client-server latency caused the whole UI to break (probably the limits of setTimeout reached? :-)). If you check the github issues, it's just ignored problems and they are focus on releasing new functionality instead of fixing the issues. Doesn't really motivate to report anymore problems. They had one good thing: they would allow you to work in sql and write efficient queries, but clearly they decided it's time to remove the last good feature and now only want graphical query builders. If you use metabase: deploy it on a replica such it doesn't whack your prod DB. And take backups before upgrading, because there is no revert. I've spent enough time on Metabase problems, won't touch it anymore.
- salsakran 7y ago
  I'm on the Metabase team - We've walked a fine line between fixing bugs, adding the features that our users have asked for and building out the BI interface we think the world should be using in 5 years. We don't always get it right, and I'm sorry if we broke things for you on the performance side. We will be spending a few of our development cycles after 0.33 to try to clear out our bug queue. One specific factual point I'd like to reply to however - SQL isn't going anywhere. If anything we're making it easier to both write plain SQL, use SQL templates or use our graphical interface on top of SQL query results in our next release (preview at https://github.com/metabase/metabase/releases/tag/v0.33.0-preview2 https://github.com/metabase/metabase/releases/tag/v0.33.0-pr...)
westpfelia 7y ago
Is there anyway to use a BI tool like Metabase and combine it with Qradar? I'm interested in being able to create useful reports.

tdhz77 7y ago

I’m still using informixDB so the bring your own jbdc connector maybe what I was looking for in Poli.