Point a BI tool at Airbrx
Pick a tool, change one connection setting, run a query.
The whole Airbrx pitch lives in this step. Whatever your data tool was connecting to before — your Snowflake or Databricks hostname — change it to your gateway address from step 2. Same credentials, same SQL, same results. Run any query and traffic appears in the tenant's traffic page.
Pick a tool
Each recipe walks through the connection-string change for a specific tool. Pick whichever you actually use; the others wait their turn.
Tableau
Snowflake or Databricks connector — change the Server field.
Power BI
Snowflake or Databricks connector — change the Server field.
Excel
Power Query / Get Data — change the Server field.
DBeaver
JDBC URL change. Cleanest demo because DBeaver shows headers natively.
dbt
profiles.yml update. Pair with invalidation rules.
Python & JDBC
snowflake-connector-python, databricks-sql-connector, JDBC.
If you're just kicking the tires, use DBeaver
DBeaver shows the X-Airbrx-* response headers right in its
session log — no App, no extra tooling. Run a query twice and you'll see
the second one come back with X-Airbrx-Cache-Status: HIT.
It's the fastest path to the "huh, that's actually working" moment.
What you should see
Run any query through the tool. The tenant's traffic page in the App
starts populating — every query the BI tool sends shows up with its
timing, cache outcome (currently all BYPASS or
MISS because there are no rules yet), and identifying user.
That last detail matters: if traffic is appearing in the App, the gateway address is reachable, the warehouse adapter is working, and credentials are passing through correctly. End-to-end Gateway is live. The only thing left is to actually cache something — that's step 5.
If something goes wrong
- The tool can't reach the gateway address. Re-check the hostname — typos are the usual culprit. The gateway address uses TLS on the standard port; no special port configuration needed.
- Authentication fails. The Gateway forwards your warehouse credentials, so if they fail, the warehouse rejected them. Verify they work directly against the warehouse first.
- The query fails with an unexpected error. Check the tenant's traffic page — the App captures the request and surfaces warehouse errors. Often it's a permissions issue on the warehouse, not Airbrx.