<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Iceberg on saahityaedams</title>
		<link>https://saahityaedams.github.io/tags/iceberg/</link>
		<description>Recent content in Iceberg on saahityaedams</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://saahityaedams.github.io/tags/iceberg/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>S3 Table Metrics System</title>
				<link>https://saahityaedams.github.io/posts/drafts/metrics/</link>
				<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://saahityaedams.github.io/posts/drafts/metrics/</guid>
				<description>&lt;p&gt;When working at a large tech company, one thing I really enjoyed and found useful was that if you had a question about some aspect of the system (like say the cache ratio), all you had to do to get an answer was emit a metric in the code with a library, deploy and see the live data flow into some internal embeddable version of cloudwatch. The developer experience was particularly good since from my POV all I had to do was use the library in my service and emit a metric and everything else worked out of the box. My sense is that this was an internal implementation of canonical log lines&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; since I recollect seeing these metrics in the boxes where the logs were collected as well.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
