News for hackers. Stuff that matters.
Re:Python at Netflix by Tycho on Tuesday April 30, 2019 @12:51PM (#19789608)
Does anyone have more info about this or know of similar projects?

We lean on the many of the statistical and mathematical libraries (numpy, scipy, ruptures, pandas) to help automate the analysis of 1000s of related signals when our alerting systems indicate problems. We’ve developed a time series correlation system...

Re:Python at Netflix by jamespo on Tuesday April 30, 2019 @12:59PM (#19789699)
There's https://prometheus.io/ which you're probably familiar with
Re:Python at Netflix by aaronblohowiak on Tuesday April 30, 2019 @02:20PM (#19790528)
What would you like to know?
Re:Python at Netflix by Tycho on Tuesday April 30, 2019 @03:35PM (#19791143)
The correlations part specifically, what does it do, what’s the modelling approach, and is there more info about it anywhere?
Re:Python at Netflix by relix42 on Wednesday May 01, 2019 @10:38PM (#19804084)
Initially we wrote the library to help us answer the question about what change may be causing impact to our customers' experiences. Out of the billions of time series metrics we have we knew there were about 10,000 or so likely (for this initial use case), possible candidates and we wanted to reduce that set as far as possible and either (1) find /the/ candidate for problem or (2) produce a short list of things for the humans to look into. In order to get to the point where we could ensure high likelihood of apropos correlations, we needed to do some work on the signals first.

First we detect if any of the possible candidate signals were born or died in the interesting time period. We use these time points to reduce the window we'll use to pass to the correlation functions. We can also detect any changepoints in the time series and apply similar logic. Once we've determined the best window bounds for each candidate signal, we use pearson and spearman correlation functions to get a score for the pair of signals -- the initial signal that started the inquiry and the candidate signal using the determined time window.

The code is about 98% data preparation, signal analysis, and window determination and about 2% correlation work.

(I've tried to summarize quite a bit, let me know if you'd like clarifications or have other questions.)

Re:Python at Netflix by aaronblohowiak on Tuesday April 30, 2019 @11:24PM (#19794283)
Cool, I’ll ping the folks responsible and have them reply here soon.
Re:Python at Netflix by mistrial9 on Tuesday April 30, 2019 @05:09PM (#19791958)
push or pull ?