Author(s):	Hynek Schlawack
Location	Congo Room
Date	oct Fri 07	Days Raw Files
Start	14:15	First Raw Start	error-in-template
Duration	00:45:00	Offset	None
End	15:00	Last Raw End
Chapters
Total cuts_time	None min.

https://za.pycon.org/talks/27/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Get_Instrumented_How_Prometheus_Can_Unify_Your_Metrics.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:	Metrics are highly superior to logging in regards of understanding the past, presence, and future of your applications and systems. They are cheap to gather (just increment a number!) but setting up a metrics system to collect and store them is a major task. You may have heard of statsd, Riemann, Graphite, InfluxDB, or OpenTSB. They all look promising but on a closer look it’s apparent that some of those solutions are straight-out flawed and others are hard to integrate with each other or even to get up and running. Then came Prometheus and gave us independence of UDP, no complex math in your application, multi-dimensional data by adding labels to values (no more server names in your metric names!), baked in monitoring capabilities, integration with many common systems, and official clients for all major programming languages. In short: a unified way to gather, process, and present metrics. This talk will: 1. explain why you want to collect metrics, 2. give an overview of the problems with existing solutions, 3. try to convince you that Prometheus may be what you’ve been waiting for, 4. teach how to impress your co-workers with beautiful graphs and intelligent monitoring by putting a fully instrumented Python application into production, 5. and finally give you pointers on how to migrate an existing metrics infrastructure to Prometheus or how to integrate Prometheus therein. markdown
Comment:	production notes