<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cortex on alexos.dev</title>
    <link>https://alexos.dev/tags/cortex/</link>
    <description>Recent content in Cortex on alexos.dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Thu, 23 May 2019 18:00:00 -0100</lastBuildDate>
    <atom:link href="https://alexos.dev/tags/cortex/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KubeCon - Observability</title>
      <link>https://alexos.dev/2019/05/23/kubecon-observability/</link>
      <pubDate>Thu, 23 May 2019 18:00:00 -0100</pubDate>
      <guid>https://alexos.dev/2019/05/23/kubecon-observability/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://alexos.dev/images/monitoring.jpg?width=600px&amp;amp;classes=shadow&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;One of the (many) topics I was keen to get into while at KubeCon was &lt;strong&gt;observability&lt;/strong&gt;. This is something that is just so totally and utterly crucial when running this whole &amp;ldquo;distributed microservice&amp;rdquo; thing that you really need good solutions to this stuff to make a success of it.&lt;/p&gt;&#xA;&lt;p&gt;In the case of my team right now, we have some good stuff going on. Prometheus &amp;amp; Grafana are great - digging those a lot. We&amp;rsquo;re standardising some dashboards for teams that aren&amp;rsquo;t too fussed, and we&amp;rsquo;re also seeing some teams do some really funky things beyond that with their instrumented code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
