<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ops on Bill Glover</title>
		<link>https://old.bill.dev/tags/ops/</link>
		<description>Recent content in Ops on Bill Glover</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
			<managingEditor>hello@bill.dev (Bill)</managingEditor>
		
		
			<webMaster>hello@bill.dev (Bill)</webMaster>
		
		
		
			<lastBuildDate>Sun, 28 Sep 2025 22:27:35 +0100</lastBuildDate>
		
			<atom:link href="https://old.bill.dev/tags/ops/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Instrument Go applications with Wavefront</title>
				<link>https://old.bill.dev/2020/07/17/instrument-go-applications-with-wavefront/</link>
				<pubDate>Fri, 17 Jul 2020 06:00:00 +0000</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2020/07/17/instrument-go-applications-with-wavefront/</guid>
				<description>&lt;p&gt;In the &lt;a href=&#34;https://old.bill.dev/2020/07/09/logging-metrics-its-a-journey/&#34;&gt;Part One&lt;/a&gt; of this series, I looked back at my experience with using application logs to gain insight into application and system performance. Despite the wealth of information these logs contain, much of it goes untapped. The advent of log analytics saw a step change in the information we were able to retrieve from his goldmine of untapped data. This served as a catalyst, prompting both development teams and businesses to demand more insight from their applications. But this didn&amp;rsquo;t come without challenges. The performance challenges and the coordination required to reliably obtain business metrics from log-based solutions are not insignificant. This has given rise to a new era in observability, the era of the metric.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Logging &amp; Metrics: It’s a Journey</title>
				<link>https://old.bill.dev/2020/07/09/logging-metrics-its-a-journey/</link>
				<pubDate>Thu, 09 Jul 2020 06:00:00 +0000</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2020/07/09/logging-metrics-its-a-journey/</guid>
				<description>&lt;h2 id=&#34;the-power-of-logs&#34;&gt;The Power of Logs&lt;/h2&gt;&#xA;&lt;p&gt;A few years ago, I did some work for an online retailer. The systems were complex. Over the years, the business had layered an online presence atop of systems built to serve the needs of disconnected physical stores. Change was hard.&#xA;Despite this complexity, the data used to assess eCommerce performance were remarkably simple. Most prominent were the Requests Per Second (RPS) served by the web servers. Traffic patterns were so predictable that morning dips, lunchtime spikes and absolute numbers were all familiar to the business.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Privacy Conscious Web Logs</title>
				<link>https://old.bill.dev/2020/03/31/privacy-conscious-web-logs/</link>
				<pubDate>Tue, 31 Mar 2020 20:16:35 +0000</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2020/03/31/privacy-conscious-web-logs/</guid>
				<description>&lt;p&gt;Anyone looking for statistics on their blog will find themselves pushed towards the big names in web analytics. In return for statistics, you are encouraged, if not required, to gather more information about your readers than strictly necessary. Even if you gather statistics from your server logs, you are almost certainly logging unnecessary information about visitors. It doesn&amp;rsquo;t have to be this way.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been attempting to revive my blog recently and wanted some insight into the posts I&amp;rsquo;ve published. Inspired by Laura Kalbag&amp;rsquo;s commitment not to track her readers (see &amp;ldquo;&lt;a href=&#34;https://laurakalbag.com/i-dont-track-you/&#34;&gt;I don&amp;rsquo;t track you&lt;/a&gt;&amp;rdquo;), I wondered if I could achieve the same results with my Nginx hosted blog.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
