Overview
—Single source
Pull one source now. A window is optional — leave blank for an incremental pull from the stored watermark.
Multiple sources
Land several sources in one ingestion — click to select. Analyses fire automatically once their required sources are staged, and every KPI reading what you land is recalculated behind them.
Manual upload
—Hand-feed files instead of waiting for a pull. Everything lands in one ingestion — one batch per file — so multi-source analyses fire once the sources they need have staged. Each file is archived, parsed and validated by the same pipeline a folder-delivered one goes through.
Run analysis (advanced / plugin clients)
Runs a plugin-based analysis synchronously over the current dataset. For this client the analyses are KPI configs — use the KPIs tab to run those.
New schedule
A saved trigger on a cron. Editing a schedule takes effect immediately; disabling keeps the definition but stops it firing.
Schedules
| Name | Cron | TZ | Trigger | Enabled | Next run | Last fired |
|---|
Queues
Recent batches
reap stalled > minReap rescues batches stranded by an infrastructure crash — ones stuck in a non-terminal state (started/parsed/validated) with no worker still processing them. It marks any older than the threshold as failed, so they stop hiding in limbo and can be replayed. The age floor means a batch that is genuinely still running is left alone. Open a batch's Details below to see why a failed one failed.
| Source | Status | Rows | Stage | Created | Batch |
|---|
KPI catalog
—Every figure this deployment computes, grouped by business process. Each is calculated when an ingestion stages the data it reads, so the numbers are already here — the tag on each row is how long ago it was computed.
Select a KPI
Pick one from the catalog to see what it measures, what it reads, and the figure already computed for it.
Stored findings
Persisted analysis outputs. For clients whose analyses are KPI configs (like this one) findings are empty — those results are served live in the KPIs tab.
Who can do what
Roles live on the auth server, not here — this is a view onto it, and every change is made with your credentials. The right-hand column shows what each auth-server role means in this deployment, which is decided by AUTH_ROLE_MAP: a role with no mapping grants nothing here.