Are you sure you actually read through the webpage? I haven't watched the video either, and I was able to figure it out pretty easily.
> ...analyzes the stack trace of every exception, and determines which line in the backtrace is the source of the bug.... uses git to figure out who might have caused the bug... shows you where in the code the problem was, so you can quickly get to fixing it...
So, it's an exception logger that integrates with your version control system and `git blame`.
> ...sends an email to the engineer at fault...
It emails someone when it figures out they were responsible for an exception.
> ...If the engineer sits on the email, eventually it escalates...
It messages the rest of the team if the bug doesn't get fixed.
> ...Dig inside the values of environment variables, instance variables, request parameters, and more... analyze information about a bug to determine its root cause... symbolicates iOS crashes, un-minifies JavaScript code, and de-obfuscates Java code...
It tracks data about your application, and captures state useful in digging into the cause of a bug.
> ...full-featured commenting system, ticket-management system similar to JIRA, and a news feed... PagerDuty and JIRA integration...
It has collaboration features and integration with various existing development tools.
It currently has clients for Java, Objective-C, Ruby and Javascript. So it most likely supports any application you're working on as long as that application has a git repository. Feel free to contribute a Python client.
> ...analyzes the stack trace of every exception, and determines which line in the backtrace is the source of the bug.... uses git to figure out who might have caused the bug... shows you where in the code the problem was, so you can quickly get to fixing it...
So, it's an exception logger that integrates with your version control system and `git blame`.
> ...sends an email to the engineer at fault...
It emails someone when it figures out they were responsible for an exception.
> ...If the engineer sits on the email, eventually it escalates...
It messages the rest of the team if the bug doesn't get fixed.
> ...Dig inside the values of environment variables, instance variables, request parameters, and more... analyze information about a bug to determine its root cause... symbolicates iOS crashes, un-minifies JavaScript code, and de-obfuscates Java code...
It tracks data about your application, and captures state useful in digging into the cause of a bug.
> ...full-featured commenting system, ticket-management system similar to JIRA, and a news feed... PagerDuty and JIRA integration...
It has collaboration features and integration with various existing development tools.