BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cfgmgmtcamp.org//PY3NPY
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2024-PY3NPY@cfp.cfgmgmtcamp.org
DTSTART;TZID=Europe/Brussels:20240205T155500
DTEND;TZID=Europe/Brussels:20240205T164500
DESCRIPTION:With thousands of available plugins\, Ansible automates and orc
 hestrates configuration management\, application deployment as well as clo
 ud\, network\, security and server infrastructure.\n\nBeyond these typical
  scenarios\, it can be a great abstraction layer to interface or glue diff
 erent tools and systems together.\n\nGiven this wide range of use cases an
 d the many ways they can all go wrong differently dozens or thousands of t
 imes a day\, it would be interesting and useful to have detailed and granu
 lar metrics about individual playbooks\, hosts and tasks.\n\nWe could spot
  improvements\, regressions\, spikes and bottlenecks in Grafana to make pl
 aybooks run better and faster.\nIf unexpected changes or failures happen\,
  we could notify someone or something about it with Alertmanager.\n\nIn th
 is talk we'll explain and show "why not" using an implementation that puts
  Ansible metrics in Prometheus using ARA Records Ansible.\n\nAt time of wr
 iting\, it kind of works and puts many pieces of the puzzle together but d
 oesn't quite use the right approach. It turns out putting historical metri
 cs in Prometheus is not that simple.\n\nWe might just find out how to do i
 t together if you are interested in the use case !
DTSTAMP:20260309T205136Z
LOCATION:B.3.039
SUMMARY:Putting Ansible metrics in Prometheus because why not ¯\\_(ツ)_/
 ¯ - David Moreau-Simard\, Daniel Mellado
URL:https://cfp.cfgmgmtcamp.org/2024/talk/PY3NPY/
END:VEVENT
END:VCALENDAR