<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Alex Gläser</title>
    <description/>
    <link>https://speakerdeck.com/apglaeser</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/apglaeser.rss"/>
    <lastBuildDate>2018-11-18 16:43:57 -0500</lastBuildDate>
    <item>
      <title>Are you still alive? Bringing monitoring to te devs</title>
      <description>Monitoring is not a ops native topic anymore. For scaling purposes monitoring your infrastructure and application behaviour needs to be a dev native task.</description>
      <media:content url="https://files.speakerdeck.com/presentations/6e579717e8fb4726aa18ba8a2b0a882a/preview_slide_0.jpg?11257358" type="image/jpeg" medium="image"/>
      <content:encoded>Monitoring is not a ops native topic anymore. For scaling purposes monitoring your infrastructure and application behaviour needs to be a dev native task.</content:encoded>
      <pubDate>Sun, 18 Nov 2018 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/apglaeser/are-you-still-alive-bringing-monitoring-to-te-devs</link>
      <guid>https://speakerdeck.com/apglaeser/are-you-still-alive-bringing-monitoring-to-te-devs</guid>
    </item>
  </channel>
</rss>
