<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Policy Language on Precomputing.com</title>
    <link>https://precomputing.com/tags/policy-language/</link>
    <description>Recent content in Policy Language on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/policy-language/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Policy Language</title>
      <link>https://precomputing.com/the-policy-language/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/the-policy-language/</guid>
      <description>&lt;p&gt;&lt;strong&gt;A policy is a short text file. It names the streams of events you have and the answers to keep ready, and says how long each level of detail survives.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;The compiler turns it into plain SQLite, and the Engine runs it as it is. This post walks through a policy line by line, and shows what each line becomes in the file.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://precomputing.com/images/policy-anatomy.png&#34; alt=&#34;A policy&amp;rsquo;s lines and the tables they become. raw keep 5m becomes latency_raw, whole events. Each rollup becomes rows of latency_win, one summary per window and key, and quantiles ms adds the sketch buckets in latency_ms_sk. samples becomes latency_sample, anomalies becomes latency_anomaly and latency_base, and each precompute becomes a view with its own name.&#34;&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
