<?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 RollupDB.com</title>
    <link>https://rollupdb.com/tags/monitoring/</link>
    <description>Recent content in Monitoring on RollupDB.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rollupdb.com/tags/monitoring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracking API Latency and Errors per Endpoint for a Year With RollupDB</title>
      <link>https://rollupdb.com/tracking-api-latency-and-errors-per-endpoint-for-a-year-with-rollupdb/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rollupdb.com/tracking-api-latency-and-errors-per-endpoint-for-a-year-with-rollupdb/</guid>
      <description>&lt;p&gt;A small online shop runs one API with four endpoints that matter: product pages, the cart, search and checkout. The team wants a dashboard for today. They also want to answer, next spring, whether checkout got slower after the autumn release, and whether its p99 last Black Friday was worse than this one.&lt;/p&gt;&#xA;&lt;p&gt;Request logs answer that, if you keep them. Most teams don&amp;rsquo;t keep them for a year because the bill for storing and scanning them grows every month. Monitoring tools keep the history, usually as pre-averaged numbers, and a p99 averaged across minutes isn&amp;rsquo;t the hour&amp;rsquo;s p99. RollupDB sits in between. It keeps per-endpoint counts, sums, extremes and a percentile sketch, and merges them correctly as they age.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
