<story><title>Netflix FlameScope</title><url>https://medium.com/@NetflixTechBlog/netflix-flamescope-a57ca19d47bb</url></story><parent_chain></parent_chain><comment><author>throwaway84742</author><text>I’ve done something like this at Microsoft in 2002. Except in my case it was a multi-user system and each row represented a logical user, or a range of users in a range partitioned space. You could vary granularity, click through to see what’s busted, zoom into user ranges, discover correlated failures, discover cases when something is failing for just one user consistently, correlate all of it to performance counters, etc, etc. No one gave a shit.</text></comment>
<story><title>Netflix FlameScope</title><url>https://medium.com/@NetflixTechBlog/netflix-flamescope-a57ca19d47bb</url></story><parent_chain></parent_chain><comment><author>smaili</author><text>Link to the repo -- &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;flamescope&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;Netflix&amp;#x2F;flamescope&lt;/a&gt;&lt;p&gt;From a quick glance, it&amp;#x27;s interesting to see both Flask and Node.JS be used within the same project repo. Is this becoming more commonplace?</text></comment>