<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Prometheus on TaskFused.com</title>
    <link>https://taskfused.com/tags/prometheus/</link>
    <description>Recent content in Prometheus on TaskFused.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://taskfused.com/tags/prometheus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TaskFused 0.2 Lets Finished Work Expire and Adds Prometheus Metrics</title>
      <link>https://taskfused.com/taskfused-0.2-lets-finished-work-expire-and-adds-prometheus-metrics/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://taskfused.com/taskfused-0.2-lets-finished-work-expire-and-adds-prometheus-metrics/</guid>
      <description>&lt;p&gt;TaskFused 0.1 kept every operation forever. That&amp;rsquo;s what makes joining work: a request that arrives a week later with the same key still finds the finished operation and gets its result. But a service that runs for a year piles up a year of operations, the file only grows, and a namespace with a cap on kept operations eventually hits it and refuses new work.&lt;/p&gt;&#xA;&lt;p&gt;0.2 lets each namespace say how long finished work keeps its name. Set &lt;code&gt;-identity-retention 720h&lt;/code&gt; and an operation that succeeded, failed or was canceled more than 30 days ago is deleted with its attempts and its history. Its slot is free, and the same key starts new work. Queued and running operations are never touched. &lt;code&gt;taskfused serve&lt;/code&gt; does the expiry every minute; an embedding calls &lt;code&gt;ExpireDue&lt;/code&gt; when it likes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
