<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logs Demo on Precomputing.com</title>
    <link>https://precomputing.com/tags/logs-demo/</link>
    <description>Recent content in Logs Demo on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 26 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/logs-demo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web Shop Logs Case Study: A Dashboard Sent Upstream in 120 Times Fewer Bytes</title>
      <link>https://precomputing.com/web-shop-logs-case-study-a-dashboard-sent-upstream-in-120-times-fewer-bytes/</link>
      <pubDate>Sat, 26 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/web-shop-logs-case-study-a-dashboard-sent-upstream-in-120-times-fewer-bytes/</guid>
      <description>&lt;p&gt;A web shop sends its logs to a log platform so a dashboard can show requests, latency, errors, payments and revenue, and so someone can search the lines when things go wrong. The platform charges by the gigabyte ingested and by the million lines indexed, and many of those lines are never read. In the Logs demo a log reducer sits next to the shop&amp;rsquo;s services. It learns each kind of line as it arrives, keeps every line on site for 48 hours, and sends upstream only the answers the dashboard shows, the errors and anything new.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
