Author(s):	Jamie Wilkinson
Location	D2.193 Percy Baxter
Date	feb Wed 03	Days Raw Files
Start	16:35	First Raw Start	16:33
Duration	0:45:00	Offset	0:01:13
End	17:20	Last Raw End	17:21
Chapters	00:00
Total cuts_time	47 min.

https://linux.conf.au/schedule/30131/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf An_introduction_to_monitoring_and_alerting_with_timeseries_at_scale_with_Prometheus.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Monitoring is the foundational bedrock of site reliability, and yet is the bane of most sysadmin's lives. Why? Monitoring sucks when the cost of maintenance scales proportionally with the size of the system being monitored. Recently tools like Riemann and Prometheus have emerged that can address this problem, by scaling out monitoring configurations sublinearly with the size of the system. In this talk, Jamie will talk about the theory of alert design and timeseries-based alerting methods, and complement that with practical examples in Prometheus that you can deploy in your environment today to reduce the amount of alert spam and help operators keep a healthy level of production hygiene. markdown
Comment:	production notes