<?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 BareProxy.com</title>
    <link>https://bareproxy.com/tags/monitoring/</link>
    <description>Recent content in Monitoring on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Uptime Checks and Status Pages Plugin: A Public Status Page Served by the Proxy</title>
      <link>https://bareproxy.com/bareproxy-uptime-checks-and-status-pages-plugin-a-public-status-page-served-by-the-proxy/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-uptime-checks-and-status-pages-plugin-a-public-status-page-served-by-the-proxy/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Status: planned, number 14 of 21 in BareProxy&amp;rsquo;s build order.&lt;/strong&gt; The plugins are built easiest first, and this one is two or three days of coding: checks on a timer, history in the store, a status page. It comes after the Cookie consent plugin. This post describes what it will do, and it will be updated as it is built.&lt;/p&gt;&#xA;&lt;p&gt;When a service has trouble, the first thing its users look for is a status page: is it down, is anyone working on it, when was it last fine. Most teams pay a separate service for that page, and the page knows only what its own checks see from the outside.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
