Re:Discovering Anomalies in Real-Time with Apache Flink
by urlgrey on Thursday February 16, 2017 @10:26AM
(#13660564)
I'm the author of this Mux blog post and would love to take any questions or comments, as well as suggestions for future posts. Thank you for your interest!
[ Parent
| on HN ]
Re:Discovering Anomalies in Real-Time with Apache Flink
by oxtopus on Thursday February 16, 2017 @01:37PM
(#13662345)
Can you elaborate on the "novel anomaly-detection algorithms" used here?
Re:Discovering Anomalies in Real-Time with Apache Flink
by urlgrey on Thursday February 16, 2017 @02:12PM
(#13662653)
Sure! We evaluated several anomaly-detection tools & libraries. They included:
tried-and-true statistical methods like probability density functions
Yahoo EGADS anomaly-detection library
Numenta HTM neural-network anomaly-detection library
We ruled out HTM due to AGPL licensing concerns. It's an interesting product, but wasn't a good fit for us at this point in time. EGADS and other basic statistical methods can actually get you pretty far.
Re:Discovering Anomalies in Real-Time with Apache Flink
by bradknowles on Thursday February 16, 2017 @06:44PM
(#13664690)
And what do you do with this video anomaly information?
Re:Discovering Anomalies in Real-Time with Apache Flink
by urlgrey on Thursday February 16, 2017 @10:48PM
(#13665766)
Mux (https://mux.com/) collects performance metrics for video delivery & playback on the websites & apps of our customers. These metrics feed into our real-time alerting system. If the error-rate for a customer property (site) or video-title is exceptionally high then an alert will be triggered. Mux customers can configure alert notifications to be sent to Slack & email, and view a history of alerts in the Mux web dashboard. We also offer the ability to view breakdowns of playback failures, video start-up times, and more through our dashboard. This can be helpful for diagnosing playback issues related to specific browsers, geographies, ISPs, and more.