Redash

A Keycloak SAML setup failed until the client ID was set to the callback URL, after hours of debugging.

Affects: admins configuring SAML

After upgrading from v8 to v10, Docker logs show Postgres connection errors and the user is unsure whether the service is affected.

Affects: self-hosted admins

A query raising an error is retried repeatedly, sustaining high database load, and the failure was only discoverable in a supervisor log.

Affects: teams with scheduled queries

Sharing via link or embed is limited to queries and dashboards without parameters, because parameters need access to run any query.

A user spent hours failing to build Redash on several machines before finding an upstream packaging bug and a poetry workaround.

Affects: developers building from source

The Google Analytics integration supports only Universal Analytics and fails with a permissions error on GA4 properties.

Affects: teams querying Google Analytics

Making a parameter optional currently requires a workaround inside the query logic; the reporter asks that a section can be skipped when no value is given.

Affects: query authors

The commenter is waiting for filters that let the viewer select every value at once.

A user evaluating Redash is waiting on the ability to import CSV or Excel files as a data source, as other BI tools allow.

Affects: analysts

Merging results from several data sources exists only in the paid version, and the user is waiting for it in the open-source release.

A parameter containing an apostrophe breaks the query, and users must escape values themselves.

Affects: query authors

A company uses both tools since each has a distinct feature set and neither covers all required features.

Affects: company BI users

After evaluating on-premise Redash, the commenter judged its feature set lacking and the company directionless.

After trying Superset, Metabase and Redash, the commenter chose Metabase and says Redash sometimes feels slow.