The monitor for Tableau Cloud
Know what's on fire before your execs do.
Tableau Cloud won't tell you when an extract quietly stops refreshing, a subscription goes dark, or permissions drift. Scout watches your site around the clock, ranks what broke by what it's about to cost you, and calls it in to the right person with the diagnosis and the fix in plain English.
Connects with a read-only token. About 5 minutes. Never changes anything.
Now
prod · 2m agoAutopilot is handling 3. The other 39 targets are healthy.
- 94Q3_Sales_ExecCredentials expired · 38m · 212 viewers
- 71Finance_Close_DailyQueue timeout · 1h 12m · 64 viewers
- 42RETRYINGWeb_Traffic_HourlyTransient 503 · 12m · 9 viewers
Live demo · sample data
Watch it catch a break.
This is the Scout console on a sample site. Open an incident to read the diagnosis, or approve a fix and watch it land. Nothing here touches a real Tableau site.
Right now
Three things need you before 8:00 AM. 1 watched, 83 data sources healthy.
Needs you · 3
Scout is on it · 0
Scout isn't working on anything right now.
Watching · 1
Resolved · 1
What silence costs
The dashboard didn't break. It just quietly stopped being true.
A failed refresh doesn't throw an error at the person reading the dashboard. It shows old numbers with a straight face, and you hear about it from the most senior person who noticed.
- Mon 2:10 AM
The revenue extract fails. Expired credential. Tableau logs it and tells no one.
- Tue to Thu
It fails every night. The dashboard still loads, so it looks fine. It just shows Sunday.
- Fri 8:52 AM
The CFO opens it to prep the board. The numbers don't match finance's spreadsheet.
- Fri 9:05 AM
You get the message. You find out the same way everyone else did.
Right after the first failure: the cause, the owner, the dashboards it feeds and the fix, before anyone opens it.
Not hypothetical. The Friday before Labor Day, Tableau Bridge stopped refreshing a 600+ user environment. Nothing showed as failed. Scout flagged it 17 minutes in, and it was healthy 28 minutes later, before a single client noticed.
How it works
Not a dashboard you have to remember to check. A loop that runs against your site all day.
- 01Baseline
Learns each target's normal: run time, cadence, who views it and when.
- 02Detect
Watches every background job, publish rhythm and subscription for a deviation.
- 03Triage
Classifies the root cause and scores it by what it's about to cost you.
- 04Call it in
Routes the diagnosis and the fix to the owner, in plain English.
Get to the root cause in minutes, not a morning
Open a forensic session on a single failure: what else failed with it, whose content it hits, schedule drift, upstream and downstream. Each one writes a case file. Read-only.
Let it fix the safe stuff, and nothing else
Autopilot only acts where you said it could: by site, project, datasource tier or owner role. Anything outside the guardrail goes to a human.
Get through security review
JWT Direct Trust via a Tableau Connected App, site-level for REST and tenant-level for the Platform Data API. No passwords stored, read-only by default.
HeatScore
Severity is what broke. HeatScore is what it's about to cost you.
Tableau ops teams drown in alerts that are technically severe and operationally trivial. HeatScore answers the only question that matters at 5:30am: which one do I call in first?
- 01
- Time-to-view
Heat cools overnight and climbs as scheduled view-times approach. A 5:30am failure on a 9am exec dashboard is a 95. The same failure at 6pm is a 12.
- 02
- Datasource fan-out
A datasource feeding 40 workbooks heats faster than one feeding a sandbox. Scout walks the dependency graph for you.
- 03
- User and department exposure
Which dashboards execs open, which ones finance touches at quarter-close, which ones marketing watches in the morning. Heat scales with who's about to look.
- 04
- Trust history
If Scout has cried wolf on an asset before, that history dampens the score. It earns its weight back.
Q3_Sales_Exec extract fails. 212 viewers, 9am exec review, 14 downstream workbooks.
drag across the bars or use ← → to move the failure
Modes
Scout watches. You decide how much it does about it.
A monitor that only pings you is noise. Scout makes the call on the deviations Tableau Cloud won't surface, and hands them to the right human. Autopilot is the paid action arm you switch on when you're ready to close the loop automatically.
Scout is installed but watches silently. No Slack pings, no incidents opened, no surprises. The audit log stays empty.
- Connected App auth verified
- Inventory synced from Tableau
- Audit log ready
Scout watches refreshes, queues and datasources. It opens incidents with a HeatScore, identifies the owner, drafts the diagnosis and calls it in to Slack with the fix in plain English. Eyes on, hands off.
- RefreshWatchdog detector live
- Plain-English diagnosis to Slack
- Append-only audit log
- Hosted dashboard and cross-site view (Plus)
Close the loop. Autopilot runs the lowest-risk plays automatically, inside the guardrails you set per scope, tier and owner. Includes Investigate for one-failure-at-a-time deep dives. Same audit log.
- Investigate for forensic deep dives
- Auto-retry safe refreshes
- Re-embed dropped credentials
- Escalate anything outside the guardrail
Pricing
Hosted, fully automated, or inside your network. One ladder.
Start with Plus for the hosted dashboard and managed alerts. Add Autopilot when you want failures fixed without a human in the loop. If Scout has to run inside your own network, Enterprise puts it there. Every paid tier is a 30-day pilot. Or start with a free site review, no card.
Connect your site read-only and get a report on what's at risk in about 5 minutes. If you want Scout to keep watching, turn on free monitoring from the report: the full product for 7 days, then monitoring, alerts and the incident board stay free. No card.
Connects with a read-only token. About 5 minutes. Never changes anything.
- Hear about a broken refresh before your users do, in Slack or email
- Know what broke, who it hits and the fix, in plain English
- Live the same day: connect your site at signup, nothing to install
- Every site's health on one screen (up to 5 sites)
- Answer “when did this start?” months later (full history, never trimmed)
- A real person answers within 48 hours
- Everything in Plus
- The safe failures fixed before you wake up (Autopilot, autonomy 3 to 5)
- Work the failure that matters first (HeatScore ranking)
- Root cause in minutes, not a morning (Investigate)
- Pages land where your team works: PagerDuty, Teams, Jira, ServiceNow
- Every site covered (unlimited, volume pricing past 5)
- A direct line to the founder
Run the Plus pilot first and switch on Autopilot when you're ready. No second signup.
- Scout runs inside your network, for Tableau Server behind a firewall
- Your Tableau token stays in your environment; nothing reaches TableauOps
- Security review and procurement handled with you
- Scope and deployment planned together
- A direct line to the founder
FAQ
What admins ask before turning Scout on.
Stop being the first responder. Be the second pair of eyes.
Scout has the diagnosis waiting before standup, hosted with Plus or inside your own network with Enterprise. Add Autopilot and it closes the loop on the safe stuff while you sleep. If the pilot doesn't earn its keep, cancel for a full refund.
Connects with a read-only token. About 5 minutes. Never changes anything.