Alert detection in IoT using broadcast state.
summary
Describes how Trackunit uses Apache Flink to detect alerts for over 500K IoT devices governed by 50K+ rules, including single-asset checks, fleet-wide rules, attribute validations, and geo-fencing with advanced scheduling. Explains their design using Flink broadcast state, challenges encountered with broadcast state, scalable geo-fencing implementation, and a runtime mechanism to enable/disable per-rule tracing for debugging distributed stream processing.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:27What is an alert rule
- 5:29Alert rule predicates
- 8:39Pros/cons
- 12:20Debugging
- 13:20Trace flag
related talks
38m7 reasons to use Apache Flink
35mEvent Streaming Architecture for Industry 4.0
31mUnderstanding the Real World: Streaming Analytics for IoT
49mDesign patterns for distributed client server systems via IoT
15mSecurity monitoring for connected devices across OT, IoT, edge, cloud
33mFlink for Everyone: Self-Service Data Analytics with StreamPipes
30mThe Hunt for Major League IoT-ICS Threats: A Deep Dive into IoT Threat Terrain
27mFlowFence: Practical Data Protection for Emerging IoT Application Frameworks
