Superset Version
You can check your superset version in the app interface or through the server terminal. Knowing this build number helps your team track features, fix bugs, and plan safe upgrades. Teams often give admins broad server roles just to check system details and run updates. Broad roles create risk because those same accounts can also read sensitive database records. How to check your superset version and manage updates Every deployment runs a specific release build that controls how charts and das
Version: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
You can check your superset version in the app interface or through the server terminal. Knowing this build number helps your team track features, fix bugs, and plan safe upgrades. Teams often give admins broad server roles just to check system details and run updates. Broad roles create risk because those same accounts can also read sensitive database records.
How to check your superset version and manage updates
Every deployment runs a specific release build that controls how charts and dashboards work. Users can find the release number inside the main help menu in the browser. Platform teams also check the build details from the host server command line. The app stores its metadata in a backend database that tracks schema changes. When you upgrade to a new release, the app updates those internal metadata tables. You must match your database drivers to the exact release you run. If a driver does not match, chart queries fail or return broken results.
Teams usually test a new release in a staging workspace before updating production. First, engineers back up the metadata database so they can roll back if needed. Next, they pull the new container image or package onto the staging host. Then they run the schema migration job to update the internal tables. After that, analysts check key dashboards to confirm that every chart loads fast. Once the team trusts the build, they repeat these steps in the production workspace.
Why native superset version roles leave data gaps
Keeping your software up to date fixes known security bugs in the web app. Native roles also let you control who can view dashboards or open the SQL editor. This setup works well to decide who logs in and which menus they see. Still, the app still connects to your data warehouse using shared service accounts. Every analyst who uses that data source runs queries through the same database user.
Native roles decide who logs in, not what individual queries do in flight. If you turn on the SQL editor, an analyst can query raw tables directly. A broad database role lets that user pull emails, phone numbers, or card numbers. The database audit log only shows the shared app account, not the actual person. When an upgrade goes wrong, engineers often log in directly to the backend database. Without strict query rules, a tired engineer can drop a table during a late upgrade. Masking that rewrites matched fields in results helps reduce what raw queries expose.
Version: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Best practices for safe analytics upgrades
Good release habits protect both your charts and your underlying data sources. Pin your container tags or package builds so every server runs the same code. Never use a floating tag in production because unexpected updates can break custom charts. Schedule regular checks to compare your current build against the official release notes. Read those notes carefully to spot any breaking changes in database drivers or permissions.
Separate the roles that manage server updates from the roles that query business data. An engineer who upgrades the app does not need permission to read customer tables. Give the app itself a read-only database role for all chart and dashboard queries. Use a separate account with schema rights only when you run metadata migrations. After the migration finishes, switch the system back to the restricted account right away.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Where do I find the superset version in the web interface?
Log in to the workspace and click the settings or info menu at the top. The about section displays the exact release number and build metadata on screen.
Do I need to back up metadata before upgrading?
Yes, always back up the metadata database before you run any upgrade steps. Schema migrations change internal tables and are hard to undo without a clean snapshot.
Why do my database logs only show one user for all chart queries?
The app connects to each database using one shared service account credential. The database sees the shared app account instead of the individual user who clicked.