Levitate - Last9's managed TSDB is now available on the AWS Marketplace
Levitate - Last9's managed TSDB is available on AWS Marketplace.
Operations | Monitoring | ITSM | DevOps | Cloud
The Place Where Modern Operations & Technology Come Together
The latest News and Information on Service Reliability Engineering and related technologies.
How to use Key-Based Deduplication in Squadcast | Deduplication Rules | Squadcast
Key Based Deduplication is an efficient way to avoid duplicate entries when processing incoming Events alongside existing Incidents. It generates a Deduplication Key using a user-defined template specific to events from an Alert Source. This key helps identify and group duplicates. This video explains how does Key Based Deduplication work and how to set it up effectively.
Helm Dry Run: Guide & Best Practices
Kubernetes, the de-facto standard for container orchestration, supports two deployment options: imperative and declarative. Because they are more conducive to automation, declarative deployments are typically considered better than imperative. A declarative paradigm involves: The issue with the declarative approach is that YAML manifest files are static.
Sponsored Post
Managing On-Call Rotations: Navigating Incident Management from Chaos to Calm
Navigating On-Call rotations can often feel like taming a storm of alerts and constant disruptions, leaving teams overwhelmed and stressed. Hence there is a need to streamline On-Call rotations and leverage concerned software to restore order and peace. In this guide, you'll explore practical tips, best practices, and smart strategies to transform your Incident Management process. Let's get to a more efficient On-Call experience.
PromQL Macros in Levitate
Define PromQL Macros to standardize complex PromQL queries in Levitate.
GCP Managed Service For Prometheus vs. Levitate
A detailed comparison of Levitate and Google Managed Prometheus - Cost, Scale and Ease of Use.
A case for Observability outside engineering teams
Observability is being built by engineers for engineers. In reality, o11y is for all.
We Need to Talk About the Hero Pattern Among SREs
Let’s be honest. When you see an alert pop up on your phone, you aren’t thinking “according to section 12 of our most recent SRE handbook used at training 6 months ago I need to keep in mind who should be Incident Commander and who should be Ops Lead”. You’re an engineer at heart.
Understanding the Rasmussen model for failures
What does the Rasmussen model teach us about Site Reliability Engineering?
But It's Not Our Fault! When Third-party Incidents Affect Your Service
Very few SaaS products exist completely independently. Between cloud service providers, payment processors, content delivery networks, and more, chances are you rely on external systems to keep your product working. When these systems fail, it can leave you feeling pretty helpless. In some cases you might have fallback options, but oftentimes all you can do is wait for recovery and clean up the fallout.