knobit.org

C4 (2 points)

edu:Question

https://knobit.org/id/task/dii-event-rule-tuning/C4

Also as Turtle · JSON-LD · RDF/XML

dcterms:licensehttps://creativecommons.org/licenses/by/4.0/
owl:sameAshttps://bitbucket.org/reffa/ontology/id/task/dii-event-rule-tuning/C4
rdfs:labelC4 (2 points) en
schema:hasPartdii-event-rule-tuning C4: a lagging feed nobody is told about, lag alert added
schema:hasPartdii-event-rule-tuning C4: allowed lateness cut below the observed lag rejected
schema:identifierC4
schema:position4
schema:textThe feed, 1 each. (a) On 9 October the stream ran up to 40 minutes behind while events kept arriving, so the silence alert stayed quiet: the feed's lag is unwatched. A lag condition (consumer lag or event-time delay over a stated limit, e.g. 10 minutes) is added with an owner, and the silence condition is kept. (b) CH-2 rejected: a 5-minute allowed lateness would have discarded the 9 October events, which arrived up to 45 minutes late; allowed lateness stays at least as long as the observed lag (60 minutes kept, or longer) and late events are re-evaluated on event time, not dropped. en

Used by

has questionInstant payments rule tuning before go-live - expected volumes, double cases, typologies and a lagging feed (event rule design skills)
schema:isPartOfdii-event-rule-tuning C4: a lagging feed nobody is told about, lag alert added
schema:isPartOfdii-event-rule-tuning C4: allowed lateness cut below the observed lag rejected