Skip to main content

Introduction to Site Reliability Engineering (Azure)

I'm exploring different avenues of networking besides straightforward "Work on a network, stay late every day, no peace of mind, fight with higher ups to get resources.".

You may have noticed that there's a smattering of UX and HTML/Javascript coding on here. I like coding, but I'm not too knowledgeable yet. UX is what I really enjoy (And I'm even working with a major company to improve theirs).

Site Reliability Engineering seems to be a nice merging of the two. I imagine it's who you call when your eCommerce check-out services craps the bed.

Not naming any names.



Site Reliability Engineering (SRE) is "Let's make sure our systems stay up and functional for operations". Not much different than networking to the end user. "Does the service stay up long enough for me to use it? Can I depend on it to remain upward."

A good point to remember is most systems don't need to be up all of the time. You don't even want that. It may not be fine to sleep through 5 calls about an outage at 2 PM on Tuesday, but it's okay to know that some failure is normal.

There are even 'error budgets' - If a system is up 85% of the time, that works for some machines, and you can tinker a bit with new features. If something goes down, you're still within 'budget'.

Everyone needs rest - Even machines. If you're afraid to turn something off because "We might lose everything!", you have not integrated decent backup or maintenance practices.

SRE was started with a software engineering mindset, which surprised me...at first. In retrospect, it makes sense. Software developers have to make sure their programs don't have vulnerabilities that impact gathered data, underlying hardware, and operations.

A big part of SRE is "Well, is this system sufficient enough so people have time to improve it, or are they always putting out fires?"

It's a short segment, and I encourage you to read it!

Comments

Popular posts from this blog

Making KPI Dashboards with PowerBI

 While this is the free tier, I cannot share or collaborate with others, nor can I publish content to other people's workspaces, but they will not stop me from screenshooting and recording these self-taught adventures,so! I'm doing this because I idly searched "Mattel careers" and "Information Technology", and seeing a bulletpoint saying the following: Analytical and reporting skills such as creating dashboards and establishing KPIs such as experience with PowerBI, Cognos, Tableau, and Google Data Lake/AWS is preferred And thought "Well, I've used Tableau, and I've heard about PowerBI,  even if its in-demandness is questionable , so how similar is it? And can I write about it?"  First, PowerBI (PIB) does have a downloadable, local version, but apparently Windows-only. I could download the .exe but I couldn't run it / drag it to applications on my MacBook.  Not a problem, we'll use the online SaaS version, and a dataset found here, ...

A 2-week Trial of T-Mobile Home Internet

     The Xfinity app showed usage of the past 3 months: We used less than 40% each month, for about $80 USD a month.   No thanks! That cuts into the movie budget! Before we save some money (about $15/mo), let's test how T-Mobile Internet unlimited data works for 2 weeks.    There are 15 devices for this test; Smart TVs: 4 Laptops: 4 Printer: 1 Smart Home Speakers: 3 Game Consoles: 1 Phones: 1 (There are other phones in the home but they stick with data) Other: 1 Total : 15  I made tables for 3 entries a day across 3 days to test the Xfinity service we have. Here's one;   Xfinity is pretty speedy - Download times are between 227 - 236 Mbps, Latency between 24.5 - 25.5, Jitter between 5 - 6.68, and 0 packet loss.  Let's quickly define the terms in the table;    Date/Time - The date and time of the data gathered. Download (Mpbs) - How fast your network gets data. Upload (Mbps) - How fast your network uploads data. Latency ...

Recon and SSID - Mapping With VisiWave Site Survey

My laptop is refurbished. I've written about how there are a few ... quirks. Being a technology professional, I felt okay with adopting an older machine, knowing I had the skill to fix moderate issues. From dying drivers to monitor massacres, I've ID'd, solved, and documented a lot of issues.  The newest one was my Wi-Fi adapter dropping the connection to a specific extender. While troubleshooting, I was curious about doing recon of WiFi networks and broadcasting devices anyway. That issue? A power setting. It was so determined to save power, it would disconnect. The extender is also flirting with the older end of 6 years old.  The battery needs to be replaced, but that's new to me. As a Windows laptop, there are a plethora of options to pick. How do you decide which one is safest?  I am suddenly concerned about this despite having 3 unofficial, 15$ Macbook Air chargers from eBay, and no explosions. But let's move onto the Site Survey - Where can I find the stronges...