I also found Superset unintuitive to use and setup as well. I settled on standing up Metabase because it was so simple to get started with trying it since it can be launched as a single jar. The business users loved it and so did I and administration with a Postgres backend instead of the internal h2 database was a breeze.
Metabase is great. It truly is a BI tool. Superset is more of a visualization platform, which works great if you have engineers building reports. Less good if you expect more junior analysts to be super productive.
We ran into the same exact issue with Superset not being intuitive, just for a different audience that is more technical. Also went with Metabase which is good, easy to use, lacks some a few chart types but overall the past year has seen quite a few changes and bug fixes consistently happening.
My experience with Superset was the opposite. It's easy to install using containers. You can have it up and running and connected to ClickHouse in a few minutes. I also found the internal design pretty intuitive--the SQL query lab is much easier than Grafana's editor.
I like Grafana too, but there's basically no isolation between your query and the SQL database at least in the Altinity Grafana plugin for ClickHouse which is the main one I use.
I had the same experience. Featurewise Superset looked better, but after wasting a couple of hours trying to install it, I just gave up.
Instead I installed Metabase in 5 minutes tops: spin ec2 instance, whether and java -jar . I've never looked back.
The only thing that turns me off I'd that it's implemented in an obscure language. At one time I wanted to add some custom postprocessing to an api (given an sql query, get some python/pandas postproc command from a sql comment and execute it in the returned table), but the used language is just not for me (some lisp dialect)
