https://wiki.dafne.bi-services.sk/index.php?action=history&feed=atom&title=Daily_supervisionDaily supervision - Revision history2026-10-23T19:26:00ZRevision history for this page on the wikiMediaWiki 1.34.4https://wiki.dafne.bi-services.sk/index.php?title=Daily_supervision&diff=62&oldid=prevDafne: Documentation import2026-08-06T13:36:45Z<p>Documentation import</p>
<p><b>New page</b></p><div>This page describes the routine check of a running processing. It assumes the scenarios are already configured and running unattended; the aim is to confirm that a run is progressing normally and to notice problems early.<br />
<br />
== The routine check ==<br />
Open the '''Monitor''' screen. By default it shows the currently active processings.<br />
<br />
# '''Check the executor status.''' The status button in the filter bar should read ''Running''. If it reads ''Paused'', ''Stopping'' or ''Stopped'', nothing new will start — see [[Executor control]].<br />
# '''Check for executor messages.''' The warning button next to the status appears only when messages exist. Errors reported here are produced by the executor itself, not by individual tasks, and often explain a whole processing failing to start.<br />
# '''Review the Active processings panel.''' For each processing check the status, the percentage complete and the estimated finish.<br />
# '''Look at the counters.''' A non-zero '''Error''' counter needs attention; see [[Handling failed tasks]]. A '''Warning''' counter means the tasks completed but reported something worth reading.<br />
# '''Confirm progress.''' A processing with a Running counter of zero and a Waiting counter above zero is not progressing. See [[Investigating a stalled processing]].<br />
<br />
== Reading the estimate ==<br />
For each running processing the panel shows a percentage complete and an estimated finish time, calculated from the recorded average runtime of the tasks involved.<br />
<br />
Treat the estimate as an indication, not a commitment. It is only as good as the run history behind it:<br />
* a processing running for the first time, or after a large change to the task list, has little history to work from<br />
* a run that is behind because of a failure will show an estimate that assumes normal execution from that point on<br />
<br />
Where no history is available, the panel says so rather than showing a misleading number.<br />
<br />
== Deciding whether a run is late ==<br />
Compare the estimated finish against the time the downstream consumers expect the data. If the run will not make it:<br />
* check whether the delay comes from a failed task that has been retrying — see [[Handling failed tasks]]<br />
* check whether tasks are waiting on resource limits rather than dependencies — see [[Resource management]]<br />
* if the delay is structural rather than a one-off, analyse it properly instead of intervening every morning; see [[Analysing processing performance]]<br />
<br />
== Narrowing the view ==<br />
On an installation with many scenarios the default view is too broad for a quick check. Useful narrowing steps:<br />
* use the '''Processings active today''' button to restrict the list to the current day<br />
* add a '''scenario''' or '''group''' filter chip to follow one part of the workload<br />
* use the '''tag''' filter to follow the tasks that feed one consumer — see [[Tag]]<br />
* type into the text box to jump to a task by name or ID<br />
<br />
Filters combine, and each is shown as a chip that can be removed individually.<br />
<br />
== Following a dependency chain ==<br />
When a specific output is late, select the task that produces it and open the '''Backward''' tab. It lists what the task is waiting for, with each entry's current status. Clicking an entry moves the panel to that task, so the chain can be walked back to whatever is actually blocking it.<br />
<br />
The '''Forward''' tab does the reverse, which is the quicker way to answer "if this task fails, what else is affected?".<br />
<br />
== What not to do during a run ==<br />
* Do not change dependencies while a processing is running. Dafne checks for dependency cycles when a processing is planned, not while it runs, so a cycle introduced mid-run will not be detected and will have to be resolved manually. See [[Dependencies]].<br />
* Do not use '''Set complete''' to move a run along unless the work the task represents has genuinely been done. Dependent tasks will start on the assumption that its output exists.<br />
<br />
== See also ==<br />
* [[Monitor console]]<br />
* [[Handling failed tasks]]<br />
* [[Investigating a stalled processing]]</div>Dafne