Glasnostic

Well-argued post on how "big" problems in complex systems are a combination of "small" problems, which can be fixed individually. Key question, though: what keeps these fixes from combining with other "small" fixes to new "big" problems? Looking forward to a follow-up post.

Overload needs immediate attention. Learn how Glasnostic can calibrate load patterns and notify your team via a smart integration with, e.g., @pagerduty: buff.ly/3zw9hrE #SRE #IncidentResponse #PagerDuty

All apps today are "Franken-apps": complex functionality that's stitched together from various existing and new components. This is great for the business (speed!) but also creates operational complexity that must be managed. buff.ly/3OdFqIS

We live in an automation-rich world and none of these automations are designed to work together. buff.ly/3cE41cu #SRE #CloudComplexity

Honored to have been a launch partner since the preview days! buff.ly/3PW8JRf

@MichaelCRaeder And correct 😉

@glasnostic Automate, but verify. 😎 #DevOps

No matter how well you plan and how much you automate—ultimately, unpredictability reigns supreme. There are a lot of “unknown unknowns,” so it's important to detect these quickly and react to them immediately. #clouddependencies #SRE #unpredictabilities

Explore what chaos engineering is and how it is not only a good but essential practice for distributed applications: buff.ly/2M8OWzQ #microservices #devops #operations

In our increasingly complex environments, manual debugging is not a feasible approach. What's needed is real-time visibility into the complex interactions of systems and the ability to control these behaviors. #DevOps #operations buff.ly/3uWlnaX

Honored to be a launch partner with the fantastic Azure GWLB team! Whether you’re already managing East/West flow or not, there is simply no better way to control North/South flows.

What are emergent behaviors and why do they need to be detected and controlled in real-time? buff.ly/3IKGUsP #architecture #microservices

Nothing kills application reliability like a good dose of overload. One way of dealing with this is to build a proprietary load shedding framework like @Linkedin's Hodor. But can we do more than that? buff.ly/3cormig #SRE #cascadingfailures

At the limit, all software behaves unexpectedly.

Runtime control simplifies automation, reduces toil, and minimizes unpredictability. buff.ly/3NX1iYK #SRE #CloudOps

We run every more pieces in ever more places. This requires a different kind of visibility and runtime control. buff.ly/3c6h46j #SRE

We may have "2-pizza" teams but, in the cloud, no app is an island. Everything is a dependency so our success depends on everything. How do you control what you don't own?

Site reliability engineering is hard enough, so don't handicap yourself with poor tooling. Make sure you have everything you need! #SRE #Cloud buff.ly/3OdFqIS

Have you ever gone down the root cause rabbit hole, only to discover that there was none? Generic mitigation beats searching for and fixing "root causes" every time. buff.ly/3yAhkBQ #SRE #Remediation #DevOps #Operations

@tkunze, our founder, discusses a few of the "monsters" that Glasnostic seeks to "slay" with our runtime control solution.

Your application might run well in pre-production, but what will happen after it gets released and "punched in the face" by countless other factors out in the cloud?