<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Monitoring on Ricky Moorhouse</title>
    <link>https://rickymoorhouse.uk/tags/monitoring/</link>
    <description>Recent content in Monitoring on Ricky Moorhouse</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Mon, 09 Nov 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rickymoorhouse.uk/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Monitoring API Connect - 2020 update</title>
      <link>https://rickymoorhouse.uk/blog/2020/monitoring-apic/</link>
      <pubDate>Mon, 09 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2020/monitoring-apic/</guid>
      <description>&lt;p&gt;Even though a lot has changed within the API Connect product and the types and numbers of stacks we&#39;re running since I first posted an overview of &lt;a href=&#34;https://rickymoorhouse.uk/apic/monitoring/&#34;&gt;monitoring API Connect&lt;/a&gt; , the main areas we  monitor haven&#39;t.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Trawler - Metric gathering for API Connect</title>
      <link>https://rickymoorhouse.uk/blog/2020/trawler-metric-gathering-for-api-connect/</link>
      <pubDate>Tue, 02 Jun 2020 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2020/trawler-metric-gathering-for-api-connect/</guid>
      <description>&lt;p&gt;As part of our work in running and monitoring our API Connect cloud deployments we&#39;ve built some of our own tooling to assist with monitoring what is going on within the deployments.  Trawler is one of these items which is used to gather metrics from a Kubernetes based deployment of API Connect.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introducing hem</title>
      <link>https://rickymoorhouse.uk/blog/2018/introducing-hem/</link>
      <pubDate>Wed, 25 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://rickymoorhouse.uk/blog/2018/introducing-hem/</guid>
      <description>&lt;p&gt;&lt;abbr title=&#34;HTTP Endpoint Monitor&#34;&gt;hem&lt;/abbr&gt; is a &lt;a href=&#34;https://en.wikipedia.org/wiki/Synthetic_monitoring&#34;&gt;synthetic monitoring&lt;/a&gt; tool which monitors HTTP resources on a regular schedule, storing details of the time taken and the reponse code returned.&lt;/p&gt;&#xA;&lt;p&gt;I&#39;ve been using &lt;a href=&#34;https://github.com/fzaninotto/uptime&#34;&gt;Uptime&lt;/a&gt; at work for a while for endpoint monitoring and over the time we&#39;ve been using it made a few tweaks or plugins for it - in particular being able to send metrics from Uptime to Graphite.  There were also some more substantial changes we were considering making and we&#39;d built up a number of supporting scripts to populate the checks via the Uptime API when hosts changed.  We also have all our other monitoring dashboards in Grafana. In this context I decided that what would be nice is a simple tool that could replace the checking piece and feed that data into our graphite data store to be viewed and alerted on from Grafana.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
