Page History

...

• Maintain time window of WINDOW_PERIOD, e.g. 1 hour
• Upon each incoming event, slide the window if some events in this window expire
• Compare distinct entities in current window (WIRI) with distinct entities which should be (WISB), if some entities exist in WISB but not in WIRI, then alert
• WISB can be provided or dynamic. For provided WISB, user should specify full set of entities. For dynamic WISB, user does not need specify full set of entities. Alert engine will use last WIRI as WISB

Image Added
Note: 

1) The assumption is that data always come in frequently to trigger set timestamp for time slide window. (To remove this assumption, we may need a separate background thread to trigger timestamp)

...

3) how about one node is in SA check status

Gliffy DiagramnameNoDataAlert-arch 

Absence Alert

Something must happen within a specific time range within a day. For example one type of job must be running from 1PM - 2PM every day.

...

1) The assumption is that data always come in frequently to trigger set timestamp for time window.

Gliffy DiagramnameAbsenceAlert-archImage Added

SLA alert

Some task must be completed within SLA. For example when user submits a spark job, SLA can be specified for that job, e.g. 1 hour SLA.

...