04 Job Monitoring
Job Monitoring first answers whether the work was completed, then helps locate where and when batch impact is concentrated.
What appears
| Panel | metricId or dataset | Reading |
|---|---|---|
| Failed jobs · Last 15 min | failed-jobs | Batch-error increments during the 15 minutes before the selected range end |
| Canceled jobs · Last 15 min | canceled-jobs | Unique canceled executions during the 15 minutes before the selected range end |
| Long-running jobs · Current · >120 min | long-running-jobs | Current snapshot of jobs running for more than 120 minutes |
| Long-running work processes by server | long-running-work-processes | CCMS duration in seconds, separated by server |
| Maximum long-running work processes (24 h) | long-running-work-processes | Real maximum duration over 24 hours by server; the donut contains only real servers |
| Background work processes | job-metrics | NumberOfWpBTC capacity by server as a stepped line |
| Background work-process errors | failed-jobs | ErrorsInWpBTC increments by server as bars |
| Job Runs | Jobs | Execution table and run detail |
| Job Events | Events | Job-related events |
Failed jobs does not expose the cumulative SAP ErrorsInWpBTC counter
directly. SPOT deduplicates each observation by TID and calculates positive
increments per server. After a counter reset, the new value is the increment;
when there is no recent predecessor or the gap exceeds 15 minutes, the result
is UNKNOWN. Zero is shown only when valid coverage exists.
Canceled jobs counts unique executions in (to-15m, to]. Failed jobs
uses the same range end: its KPI represents that rolling window, while its
chart retains the complete selected range. When an execution has several
matching lines, SPOT uses the last one as the outcome time; it does not assign
to the past a cancellation whose final line is later than the selected cut.
The server filter applies to that final line: if a job moved between servers,
it is not counted from an earlier line on the selected host.
Long-running jobs uses per-server XBP snapshots. The connector selects SAP
jobs in state R and counts only those running for strictly more than
120 minutes: exactly 120:00 is excluded and 120:01 is included. A fresh zero is
a valid observation; UNKNOWN means missing data, an error, or lost freshness.
SPOT does not substitute Work Process data, demo data, or an invented zero.
Long-running work processes is a duration signal in seconds, not a process count and not a substitute for running jobs.
The three functional outcomes appear as equivalent KPIs. The
Long-running work processes detail shares a composition with its 24-hour
maximum in an 8/4 ratio. The Background processing by server composition
keeps two separate synchronized charts: NumberOfWpBTC capacity above and
error deltas below. They share a time cursor, legend, and server colors, while
using independent integer axes from zero. When every covered delta is zero, the
panel explicitly reports that no errors occurred; an UNKNOWN bucket prevents
that message. Job Runs and Job Events keep their own panels; dumps are
investigated exclusively in Work Process.
In Job runs, one click selects the row and updates Execution summary.
Select Open details, press Enter, or double-click for the lifecycle and
paged job log. Escape closes the detail and returns focus to the row. Open
details is the summary's blue primary action so it remains recognizable in
both light and dark themes. The table shows 15 executions per page and translates SAP codes to Planned, Released,
Ready, Active, Finished, and Canceled; API and storage retain the code.
How to interpret it
- OK: there are no relevant failures or cancellations in the observed interval.
- WARN: failures repeat, cancellations grow, or batch pressure concentrates on one server.
- KO: impact on critical work is sustained, or job degradation coincides with batch-capacity degradation.
UNKNOWN: a fresh signal is missing. For Long-running jobs, check XBP permissions, the connection time zone, and Agent logs.
A 0 in Canceled jobs is valid when the interval was observed with no
cancellations through a successful query. If the logs Data Stream is not
available or the producer is not schema v2, the result is UNKNOWN or
producer_upgrade_required, not zero. In Long-running
jobs, 0 is also valid, but only when it comes from a successful XBP
snapshot. The same execution is not counted several times because it has
multiple log lines.
Filters and next screens
Filter by execution range, status, and server. Open Job Runs for job name, job count, and log; use Job Events for related messages. Cross-check Work Process for batch capacity and dumps, DB for latency, and Filesystem when the job writes spool, exports, or logs.
Operational use
Job Monitoring summarizes the batch outcome without requiring you to open the full table first. The three functional KPIs also appear on Landing; the remaining panels provide per-server detail and history.
For repeated failures or cancellations by job name, open Job Runs and the related events. If they coincide with high DB request time or missing batch processes, cross-check DB and Work Process before attributing the issue only to the job.