<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>SRE on Bill Glover</title>
		<link>https://old.bill.dev/tags/sre/</link>
		<description>Recent content in SRE 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/sre/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Investigating HTTP 502 responses on Cloud Foundry</title>
				<link>https://old.bill.dev/2024/08/16/investigating-http-502-responses-on-cloud-foundry/</link>
				<pubDate>Fri, 16 Aug 2024 16:27:03 +0100</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/2024/08/16/investigating-http-502-responses-on-cloud-foundry/</guid>
				<description>&lt;p&gt;As a platform engineer working with multiple platform teams running applications on the Tanzu Platform for Cloud Foundry, I have been addressing intermittent issues that have been overlooked as quirks of the platform. These issues are what I like to call developer paper cuts. They are points of friction where something does not function as expected but occurs infrequently, leading to a lack of prioritization for investigation.&#xA;One of these developer paper cuts is the occurrence of the HTTP 502 response code from services operating on the platform. In this post, I will detail our investigation into this issue, highlight some known causes of the 502 response code, and provide tips for debugging similar issues.&lt;/p&gt;</description>
			</item>
			<item>
				<title>SRE vs. Platform Engineering</title>
				<link>https://old.bill.dev/notes/getambassadorsrevsplatformengineering/</link>
				<pubDate>Sat, 07 Oct 2023 15:09:26 +0100</pubDate><author>hello@bill.dev (Bill)</author>
				<guid>https://old.bill.dev/notes/getambassadorsrevsplatformengineering/</guid>
				<description>&lt;figure&gt;&lt;img &#xA;        sizes=&#34;(min-width: 35em) 1200px, 100vw&#34;&#xA;        srcset=&#39;&#xA;        &#xA;            /notes/getambassadorsrevsplatformengineering/TeamStructure_hu_13c939acc5be5764.png 500w&#xA;        &#xA;        &#xA;            , /notes/getambassadorsrevsplatformengineering/TeamStructure_hu_49373ada72705c46.png 800w&#xA;        &#xA;        &#xA;            , /notes/getambassadorsrevsplatformengineering/TeamStructure_hu_8f755394767a1f5a.png 1200w&#xA;        &#xA;        &#xA;            , /notes/getambassadorsrevsplatformengineering/TeamStructure_hu_693dc329a514ad82.png 1500w &#xA;        &#39;&#xA;        &#xA;            src=&#34;https://old.bill.dev/notes/getambassadorsrevsplatformengineering/TeamStructure.png&#34; &#xA;        &#xA;         alt=&#34;Organisation chart showing that multiple application teams are supported by both Platform Engineering and Site Reliability Engineering teams. Application teams measure success with business KPIs. Platform and SRE teams measure success with SLOs&#34;/&gt;&lt;figcaption&gt;&#xA;            &lt;h4&gt;How application teams are organised&lt;/h4&gt;&lt;p&gt;Organisation chart showing that multiple application teams are supported by both Platform Engineering and Site Reliability Engineering teams. Application teams measure success with business KPIs. Platform and SRE teams measure success with SLOs&lt;/p&gt;&#xA;        &lt;/figcaption&gt;&#xA;&lt;/figure&gt;</description>
			</item>
	</channel>
</rss>
