<?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 Head for the Cloud</title>
    <link>https://headforthe.cloud/tags/monitoring/</link>
    <description>Recent content in Monitoring on Head for the Cloud</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://headforthe.cloud/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Is your monitoring testing strategy chaos?</title>
      <link>https://headforthe.cloud/article/is-your-testing-strategy-chaos/</link>
      <pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://headforthe.cloud/article/is-your-testing-strategy-chaos/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Nowadays, many Cloud implementations will make use of serverless architectures, such as &lt;a href=&#34;https://aws.amazon.com/lambda&#34;&gt;AWS Lambdas&lt;/a&gt; and &lt;a href=&#34;https://aws.amazon.com/api-gateway/&#34;&gt;API Gateways&lt;/a&gt; to implement micro-services, or other similar functionality to deliver business logic without the need to manage servers.&lt;/p&gt;&#xA;&lt;p&gt;This is now a mature pattern, and we have a wealth of tools and approaches to help us ensure that our serverless code is performing as expected. We can develop and test locally, and use pipelines to deploy, all ensuring the risk of deploying non-functioning code is minimised.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
