<?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 maladroit.dev</title><link>https://maladroit-dev-398201.gitlab.io/tags/sre/</link><description>Recent content in Sre on maladroit.dev</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://maladroit-dev-398201.gitlab.io/tags/sre/index.xml" rel="self" type="application/rss+xml"/><item><title>Capacity planning</title><link>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/capacity-planning/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/capacity-planning/</guid><description>&lt;h1 id="capacity-planning"&gt;Capacity-planning&lt;/h1&gt;
&lt;p&gt;Capacity planning is ensuring there is sufficient capacity and redundancy to
serve projected future demand. It is critical to take steps ensuring that
required capacity is in place by the time it is needed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Organic growth:&lt;/strong&gt; Gaining new users and adoption&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Inorganic growth:&lt;/strong&gt; Adding new features or marketing campaigns&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="mandatory-steps"&gt;Mandatory steps&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Create an accurate organic demand forecast. This should account for the lead
time to acquire capacity. Factor in inorganic demand sources into the
forecast.&lt;/li&gt;
&lt;li&gt;Perform load testing of both the systems and services&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://maladroit-dev-398201.gitlab.io/kb/reference/sre-book"&gt;SRE Book&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Change management</title><link>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/change-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/change-management/</guid><description>&lt;h1 id="change-management"&gt;Change management&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;~70% of outages are due to changes on live systems&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Automate the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Progressive roll-outs&lt;/li&gt;
&lt;li&gt;Quickly &amp;amp; accurately detect problems&lt;/li&gt;
&lt;li&gt;Rolling back safely when problems occur&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://maladroit-dev-398201.gitlab.io/kb/reference/sre-book"&gt;SRE-Book&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Monitoring</title><link>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/monitoring/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/monitoring/</guid><description>&lt;h1 id="monitoring"&gt;Monitoring&lt;/h1&gt;
&lt;p&gt;Monitoring is the primary method to keep track of a systems health and
availability. Monitoring ideally should be interpreted by software systems, not
by humans.&lt;/p&gt;
&lt;h2 id="alerts"&gt;Alerts&lt;/h2&gt;
&lt;p&gt;Alerts should only be generated when there is immediate action required.&lt;/p&gt;
&lt;h2 id="tickets"&gt;Tickets&lt;/h2&gt;
&lt;p&gt;Tickets should only be generated when there is action required, but not urgently&lt;/p&gt;
&lt;h2 id="logging"&gt;Logging&lt;/h2&gt;
&lt;p&gt;Logging should be generated when there is no action required, but there needs to
be a record for diagnostic purposes&lt;/p&gt;</description></item><item><title>Site Reliability Engineering</title><link>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/site-reliability-engineering/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit-dev-398201.gitlab.io/kb/computer-engineering/site-reliability-engineering/</guid><description>&lt;h1 id="site-reliability-engineering"&gt;Site Reliability Engineering&lt;/h1&gt;
&lt;blockquote&gt;
&lt;p&gt;Hope is not a strategy&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;A site reliability engineer (SRE) is a software engineer that focuses on solving
operational issues with software, creating Service-Level-Objects minimizing toil
of manual tasks, reduce the cost of failure, and share ownership with
developers.&lt;/p&gt;
&lt;h2 id="tenants"&gt;Tenants&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Availability&lt;/li&gt;
&lt;li&gt;Latency&lt;/li&gt;
&lt;li&gt;Performance&lt;/li&gt;
&lt;li&gt;Efficiency&lt;/li&gt;
&lt;li&gt;[[change-management]]&lt;/li&gt;
&lt;li&gt;[[monitoring]]&lt;/li&gt;
&lt;li&gt;[[capacity-planning]]&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="principles"&gt;Principles&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Embracing-risk&lt;/li&gt;
&lt;li&gt;Eliminating-toil&lt;/li&gt;
&lt;li&gt;Monitoring-distributed-systems&lt;/li&gt;
&lt;li&gt;Automation&lt;/li&gt;
&lt;li&gt;Release-engineering&lt;/li&gt;
&lt;li&gt;Simplicity&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="references"&gt;References&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://maladroit-dev-398201.gitlab.io/kb/reference/sre-book"&gt;SRE Book&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Site Reliability Engineering</title><link>https://maladroit-dev-398201.gitlab.io/kb/reference/sre-book/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://maladroit-dev-398201.gitlab.io/kb/reference/sre-book/</guid><description>&lt;h1 id="site-reliability-engineering"&gt;Site Reliability Engineering&lt;/h1&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;th&gt;&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Author&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Source&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;&lt;a href="https://sre.google/books/"&gt;Google&lt;/a&gt;&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;strong&gt;Published&lt;/strong&gt;&lt;/td&gt;
 &lt;td&gt;2016&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;</description></item></channel></rss>