About Statscraft

This conference is all about making monitoring easier, more accessible and more productive
Monitoring is crucial for detecting problems, optimizing performance, capacity planning, improving user experience and business impact... Yet in many companies, monitoring is an afterthought leading companies to miss out on the value of the data they collected. We often hear that "monitoring is hard" - and it can be, unless we do something about it.
Agenda
*this conference is Kosher and all talks are in biblical Hebrew
09:00 - 09:30
Break
Gathering and signup
09:30 - 10:15
Talk
toggle
Monitoring time in a distributed database: a play in three acts
10:15 - 11:00
Talk
toggle
How to think like an SRE
11:00 - 11:30
Break
Break
11:30 - 12:00
Talk
toggle
...But what happens when DynamoDB explodes?
11:30 - 12:00
Talk
toggle
Visualization in Serverless Applications
12:00 - 12:30
Talk
toggle
Monitoria: A monitoring democracy
12:00 - 12:30
Talk
toggle
Logging in the cloud: machines first human come second
12:30 - 13:30
Break
Lunch
13:30 - 14:00
Talk
toggle
Monitoring lessons from Waze SRE team
13:30 - 14:00
Talk
toggle
Exploiting monitoring for fun and profit
14:00 - 14:30
Talk
toggle
Monitoring done wrong
14:00 - 14:30
Talk
toggle
Spanning services - The practical guide to Distributed Tracing
14:30 - 15:30
Break
Happy hour and games
15:30 - 16:00
Ignite
toggle
Zen of production incident management
15:30 - 16:00
Ignite
toggle
Monitoring Driven Debugging
15:30 - 16:00
Ignite
toggle
Distributed HPC monitoring
15:30 - 16:00
Ignite
toggle
Actionable alerts
15:30 - 16:00
Ignite
toggle
Defining KPIs Like a Pro
16:00 - 16:30
Talk
toggle
Sensory Friendly Monitoring: Keeping the Noise Down
Organizing Committee
This conference is a community effort by and for people who do monitoring daily and care about monitoring. The organizing committee are all volunteers and sponsorships cover the direct costs of the conference.
Shlomi Noach
Staff Software Engineer @ GitHubShlomi is a developer and database geek. He is an active MySQL community member, authors orchestrator, gh-ost, freno and other open source tools, and blogs at http://openark.org. He works at GitHub on the database infrastructure team solving high availability, reliability, enablement problems, running automation and testing. Shlomi is the recipient of MySQL Community Member of the Year, Oracle ACE (Alumni) & Oracle Technologist of the Year awards.
Summary
Monitoring time is tricky given its fluid nature. Doing so across distributed database hosts is trickier. Latency, probe intervals, clock synchronization, all affect the metrics, and taking actions based on those metrics makes matters even more complex. How does one measure time? What is the baseline? What accuracy and tradeoffs can we expect? Can we use time itself to affect the outcome? At GitHub, we monitor time in our database topologies for throttling and consistent reads purposes. We present our use case and share how we communicate metric information in our distributed company.
Slides
YouTube Video