<?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 Tony Metzidis</title>
    <link>https://tonym.us/category/monitoring.html</link>
    <description>Recent content in Monitoring on Tony Metzidis</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tonym.us/category/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Testing Google Cloud Alerting with Synthetic Log Injection</title>
      <link>https://tonym.us/testing-google-cloud-alerting.html</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://tonym.us/testing-google-cloud-alerting.html</guid>
      <description>&lt;p&gt;Testing alerting in Google Cloud Monitoring requires a proactive approach, especially with uncommon scenarios. For assertions that almost always pass—such as DNS record verification or health checks—you can simulate failures using synthetic log injection.&lt;/p&gt;&#xA;&lt;h3 id=&#34;the-alerting-signal-assertion_passed-false&#34;&gt;The Alerting Signal: &lt;code&gt;assertion_passed: false&lt;/code&gt;&lt;/h3&gt;&#xA;&lt;p&gt;At the heart of this strategy is a convention: services perform their internal checks and log a JSON payload with an &lt;code&gt;assertion_passed&lt;/code&gt; boolean. When a check fails—be it a DNS mismatch or a stale cache—the service logs &lt;code&gt;{&amp;quot;assertion_passed&amp;quot;: false}&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
