01
Read-only, provably
The collector opens its database session read-only and runs SELECT statements — nothing else. There is no code path that writes to your environment.
SET TRANSACTION READ ONLY
How VizBolt works
Measured, read-only, and on your side of the network.
VizBolt works by measuring, never by asking: a claim without a measurement is a guess. The Environment Review measures your environment once, deeply. VizBolt for Splunk keeps measuring it every day. Neither ever asks you to fill in a questionnaire — and neither takes your data anywhere you can't see.
Five guarantees
02
No internet access
It makes no outbound connection of any kind. It reads, writes one file to your disk, and exits.
writes to ./vizbolt-summary.json
03
You preview before you send
The summary is a few hundred KB of counts, durations, and percentiles. You open it, read every line, and decide whether to send it.
aggregates only
04
No names, no credentials, no raw data
User names, email addresses, workbook and project names, connection strings, query text, and business data are never collected. Object names can be replaced with codes — the key stays on your machine.
key stays on your machine
05
And for VizBolt for Splunk: nothing is sent at all
They run entirely inside your Splunk. No telemetry, no phoning home, no VizBolt access — there is no boundary to cross.
runs in your splunk · sends nothing
One boundary. Three paths.
One method, two speeds.
The review: measure once, deeply
01The collector
Reads your repository. Plain, readable scripts your team reviews before anything runs — no compiled binary, no agent, no network access.
02The Environment Pack
Records your platform's shape: topology, version, licensing, key settings, and per-node hardware. Same rules — plain-text output, runs on your machine.
03You preview, then send
One summary file of counts, durations, and percentiles. Nothing that identifies people or content. You read every number, then sending it is a decision you make — not a default.
read-onlyno network accessaggregates onlypreview before send
What comes back
- Scored report. Every finding and its recommendation across the six pillars, each citing its evidence, under a Health Score always shown with its data coverage.
- Executive deck. The findings that matter, in the order they matter, written for the people who fund the fixes rather than the people who run the platform.
- Tableau workbook. Your aggregates, explorable in the tool your team already uses — filter, drill, and re-check every number behind every finding yourself.
- Prioritized action list. Owner-ready recommendations, ordered by impact against effort.
- Coverage report. Exactly what was measured, over what window — and what was not, stated plainly so no finding claims more history than it has.
Want the detail? The full method — including what each script reads — is published on the method page.
The alerts: measure continuously
Install in five minutes.
A standard Splunk app — Splunk Enterprise or Splunk Cloud.
Validate on day one.
We prove every assumption against your real Activity Log events before any alert is trusted — and you keep the results.
Alerts earn their place.
Only signals your own feed has proven get enabled; the rest switch on as their data is confirmed.
Own the thresholds.
Every number the alerts compare against lives in one editable lookup file, with per-site overrides — changes apply on the next run.
Receive in plain English.
Email, Slack or Teams — the number, the comparison it failed, and the date where one exists. Repeats throttle themselves.
runs in your splunksends nothingthresholds yoursfails silent, never loud
What comes back
- Alert in your inbox. The object, the number, the comparison it failed, and the date where one exists — readable without opening Splunk.
- Overview dashboard. Every signal's current state, browsable in the app between alerts.
- The evidence trail. Every warning timestamped next to what happened after — the record that proves the product earns its keep.
- Threshold reviews. Your numbers revisited against your real traffic as part of the subscription.
Tableau Server and Tableau Cloud
The method is the same on both platforms; only the source changes.
| Tableau Server | Tableau Cloud | |
|---|---|---|
| Access needed | A read-only account your administrator controls | A site-scoped token you create and can revoke |
| What you review | The collector's readable scripts, before anything runs | Same — reviewed before anything runs |
| Output | One aggregated summary file you preview | One aggregated summary file you preview |
| VizBolt for Splunk | Review today · alerting on the roadmap | ✓ 15 signals via the Activity Log in your Splunk |
Access needed
- Tableau Server
- A read-only account your administrator controls
- Tableau Cloud
- A site-scoped token you create and can revoke
What you review
- Tableau Server
- The collector's readable scripts, before anything runs
- Tableau Cloud
- Same — reviewed before anything runs
Output
- Tableau Server
- One aggregated summary file you preview
- Tableau Cloud
- One aggregated summary file you preview
VizBolt for Splunk
- Tableau Server
- Review today · alerting on the roadmap
- Tableau Cloud
- ✓ 15 signals via the Activity Log in your Splunk
Questions administrators ask
Do you need access to our systems?
No. Your administrator runs the collector inside your network; we never connect to your environment. On Tableau Server it uses the repository's readonly user. On Tableau Cloud it uses a site-scoped token that you create and can revoke at any time.
What if we can't send anything outside our network?
Nothing is ever sent automatically. The collector writes one file to your disk and stops. If policy blocks even the aggregated summary, the file can go through whatever data-transfer approval process your organization already uses — the engagement waits for it.
Will it affect our server's performance?
The collector runs read-only queries against the repository, not against VizQL or your dashboards. The queries are windowed and take minutes. If you prefer, run it outside business hours — the numbers are the same.
Does it work with Tableau Cloud?
Yes. Tableau Cloud has no repository to query, so the collector reads Admin Insights and the Metadata API instead. The output is the same aggregated summary file, and the same preview-before-send rule applies.
How much history do you need?
More history means better trend findings, but the collector simply reads what your retention settings have kept. Ninety days of job history is ideal; thirty is workable. Failure concentration shows up even in short windows.
Who owns the output?
You do. The report, deck, workbook, and action list are yours to share inside your organization as you see fit.
Do the alerts send anything to VizBolt?
No. They run entirely inside your Splunk. There is no telemetry, no phoning home, no VizBolt access.
What do the alerts need?
Tableau Cloud with the Activity Log feeding your Splunk — Splunk Enterprise or Splunk Cloud. Everything else we confirm with you during onboarding.
Can we tune what fires?
Every threshold, in one editable file, per site. Tuning against your real traffic is part of the pilot's first week.
Next step
See what your environment is actually doing
Explore the Environment Review →Explore VizBolt for Splunk →
Not sure where you fit? Contact us — we'll tell you in one email.