Everyone's had to endure the "last mile" of developing an application, but what happens if you consider those tasks from day 1? This talk centres around an application we released at Sky Bet earlier this year, the approaches we took, and how we benefited.
Artificial intelligence in the post-deep learning era
The Last Mile: Logging and Monitoring Best Practices
1. The Last Mile
Disclaimer: I’m only using Windows for PowerPoint. Please don’t judge.
@StephenMelrose
Lead Software Engineer - BSkyB
Photo by Ousseynou Cissé
https://www.flickr.com/photos/afuelcalledlove/
2. Are Recruiting!
Developers, DevOps, Scala/Hadoop,
Node.js Super Heroes, Principle Test Engineers,
an Engineering Manager, and more!
victoria.howling@bskyb.com
For more info, please see/contact:
33. The Syslog Protocol (RFC 5424)
DEBUG Verbose and raw debug information. Use in development only.
e.g. request/response bodies
INFO 95% of our logging. Stuff we want to monitor, e.g. HTTP request
complete, took X seconds, performed Y actions
NOTICE Similar to INFO, but significant events.
Also, errors that CAN happen and we HAVE HANDLED
WARN Errors that SHOULDN’T happen, but we HAVE HANDLED
ERROR Errors that SHOULDN’T happen and we CAN’T HANDLE
CRITICAL Fatal errors that cause the application to crash