Processors
A component is generated for each processor running on the CUE Zipline instance:
-
/processors/cue_print
for CUE Print integration -
/processors/dcx
for DC-X integration -
/processors/newsml
for NewsML export
All these components have the same structure:
{ "component": "/processors/newsml", "data": [ { "range": "15m", "count": 6, "updates": { "success": 6 }, "waiting_time": { "average": 2.7780989011128745, "max": 6.311340093612671, "min": 0.5846478939056396 } "processing_time": { "average": 0.7568506002426147, "max": 1.651845932006836, "min": 0.04902076721191406 }, } ] }
range
-
The length of the time period.
count
-
The number of events processed in the time period. This does not include events filtered out either by the global filter or a processor-specific filter.
updates
-
The outcomes of the processed events. The possible outcomes are:
-
success
(update completed, successful) -
failure
(update failed during processing) -
partial
(update completed, partly successful) -
pending
(update still in progress)
-
waiting_time
-
The length of time elapsed before events were processed during this time period in seconds. Three different values are reported: average, minimum and maximum waiting times.
The waiting time includes the common processing done by CUE Zipline to resolve an updated content item, so it can never be zero.
processing_time
-
The length of time spent processing each event, in seconds. Three different values are reported: average, minimum and maximum processing times.