Monitor¶
Watch live and recent runs across every environment, act on them in bulk, and check load and cluster health.
Before you begin¶
- The Admin area is for Flow Scheduler admins: Tableau users listed in MetaMiner Administrator (MMA) under Tools > FSS Configuration... > Admins.
- Run statuses are shown as stored, for example
RUNNINGorSERVER_DOWN. Their meanings are on Run History.
Steps¶
Watch live and recent runs¶
- In the web interface, open Admin > Task Analyze > Monitor.
- Pick a Range: Last hour, Last 24 hours (default), Last week or Last month. Runs still in progress are always shown.
- Optional: turn on Active only to show only in-flight runs (pending, submitted, running, waiting, held).
- Optional: narrow the list with the keyword and column filters above the table. The page refreshes every 15 seconds, newest runs first. Refresh pauses while you select rows. Chain rows expand to their steps.
| Column | Shows |
|---|---|
| Env, Site | The Tableau environment and site of the run |
| Task / Flow | The task or flow; a chain shows a Linked badge (for a step, its position, such as Linked 2/3). Click the name to open the flow. |
| Owner | Who created the task or chain. Direct runs from a flow's Run Now show a dash. |
| Trigger | How the run started, such as SCHEDULED, MANUAL or Catch-up |
| Schedule | The schedule that fired it; click it to open the schedule |
| Status | The run status. Runs in progress have a Cancel button. |
| Triggered | When the Flow Scheduler handed the job to Tableau |
| Started | When Tableau started running the flow |
| Completed | When the run finished |
| Wait | Started minus Triggered: time in the Tableau queue |
| Duration | Completed minus Started |
| Params | Flow parameter values sent with the run |
| Job | The Tableau job |
| Error | The error text, if any |
A Type filter (Single or Linked) is available without a column.
Act on several runs¶
- Open the Actions menu and pick an action.
- Tick the rows. Auto-refresh pauses.
- Click the action button to apply it.
| Action | Effect |
|---|---|
| Disable tasks... | Disables the tasks or chains behind the ticked runs. Future scheduled runs stop; runs in progress are not affected. |
| Delete history... | Permanently deletes the history records of the ticked runs. A chain row deletes the whole chain run. A running row loses tracking; the Tableau job is not affected. |
| Cancel runs... | Cancels ticked runs that are still in progress. A chain row cancels the whole chain run. The flows stop in Tableau; outputs already written stay. |
| Download CSV, Download XLSX | Downloads the rows and visible columns currently shown, as fss-monitor-<date>-<time>.csv or .xlsx. |
After a cancel, each run reports its outcome, for example "Cancel sent to Tableau", "Cancelled (had not reached Tableau)", "Already finished" or "Not allowed by Tableau".
Check upcoming load and capacity¶
| Page | Use it to |
|---|---|
| Admin > Task Analyze > Calendar | See upcoming schedule firings (not run history), grouped by schedule or flow. The Day view colours hours by the median Tableau queue wait of past runs, using the Yellow at, Orange at and Red at thresholds and Min samples, saved per environment. Reset restores 30 seconds, 2 minutes, 10 minutes and 3 samples. |
| Admin > Task Analyze > Load | See flow concurrency over a Window (3 hours to 1 month, default 12 hours) in Bucket steps, with an optional Reconciliation of Flow Scheduler runs against the Tableau repository. Backgrounder capacity figures appear only when loadmon.capacity.display.enabled is on. |
Load data is collected by the leader. On a standby the Load panel shows history only.
Check cluster health¶
In high availability, open Admin > HA / Nodes: exactly one node should be the leader, and every node's Last update should keep moving. The columns, Make Leader and Leadership events are described in High Availability.
Monitor from outside¶
Monitoring tools and load balancers can probe each node through its MMS address, https://<mms-host>:<port> (default port 49714):
| URL | Answers |
|---|---|
/api/flowscheduler/ready |
200 when the node is ready to serve, 503 when not |
/api/flowscheduler/health |
A JSON health document; the node's role is in custom.mmsFailover.role |
/api/flowscheduler/leader-health |
200 on the leader, 503 on a standby or when the Flow Scheduler is down |
How to use them in a load balancer: Load Balancer.
Receive alerts and read the logs¶
- The Flow Scheduler e-mails administrators when an environment's Tableau back end cannot be reached and, in high availability, on cluster events. Recipients and settings: Notifications.
- Log files and where to find them: Troubleshooting. Starting MetaMiner clears the log folder, so copy the logs first if you need them for support.
Verify¶
- The Monitor page shows runs from every enabled environment and refreshes on its own.
- In high availability, HA / Nodes shows exactly one leader and recent Last update times on every node.
Troubleshooting¶
The Admin tab is missing
Your Tableau user name is not on the Flow Scheduler admin list. Add it in MMA under Tools > FSS Configuration... > Admins, then reload the page.
A run stays in progress after Tableau finished it
Cancel it from the Monitor (Cancel or Cancel runs...), then run the task again. See Troubleshooting for each status.