Latest Posts

Chasing Log4Shell with an Automation Mindset

When zero-day vulnerabilities hit, it often feels like we have zero time to figure out the risk to our systems. Take the recent Log4Shell vulnerability as an example. By the way, Rundeck is a Java-based application, and older versions were subject to this vulnerability. If you have not yet updated to Rundeck 3.4.8 or later, please do so now. In this blog I will show you how Rundeck can be a force multiplier in helping teams quickly identify systems that need attention and take action where needed.

Avoid Alert Fatigue & Remediate Faster with PagerDuty's Rundeck and Sensu

As operators, our job is to assure that infrastructure, systems and applications are running correctly, waking up humans to fix only the things that machines can’t. With IT growing more complex and systems proliferating, it’s vital that we automate as much of our job as possible. That’s why Rundeck, a PagerDuty company, and Sensu have partnered to provide plugins and integrations combining Rundeck’s runbook automation with Sensu’s monitoring-as-code technology.

Redesigning the User Experience in Rundeck 3.4.0

Rundeck 3.4.0 includes an exciting redesigned user experience! This article summarizes the updates and provides insight into why we made the upgrades. With an internal initiative for “Building the Best Rundeck”, we set out to improve critical pain points that aim at solving problems that will benefit users of both Rundeck Community and Rundeck Enterprise.

3.4.0 What's New: UI Improvements, Plugins, ACL Updates and more!

Crisp, glossy, and crackling - I can’t think of better words to describe the new additions and improvements included in Rundeck’s 3.4.0 release (Papadum-aquamarine-book). A major theme of this release was to help make Rundeck more intuitive to learn for new users, and further simplify working with Rundeck for experienced users. If you already know Rundeck from previous releases, you’ll notice these changes right away.

From Ticket-Time to Real-Time: Changing the Status Quo of Operations Work

2020 Was...Rough. Keeping a Digital Business running has never been an easy job, especially over the last year. 2020 forced many businesses to accelerate their digital transformation initiatives faster than anyone imagined! Customers are demanding more capacity and reliability, the business is releasing more new services - faster than ever before, and companies are learning to use new remote working models, straining systems and people.

Running Operations Is Hard. PagerDuty + Rundeck Are Here to Help

Rundeck has now joined forces with PagerDuty. What pulled us together? Our shared vision for improving the work lives of those who run modern digital services. As a co-founder of Rundeck, I’d like to provide my perspective on why Rundeck becoming part of the PagerDuty family is a perfect fit for our collective user communities. No matter if you are on a “you build it, you run it” DevOps team or part of a centralized Ops team—operations work has always been difficult.

SRE Lessons: Continuously Optimize to Reduce Toil

"Can't we just automate away all of our toil?" Reducing toil is often mistaken for a linear project. The misconception is that you start at one end and refactor or automate your way to the end. In reality, reducing toil is an ongoing process. Rather than framing it as a project or special effort, reducing toil requires a continuous improvement approach.

SRE Anti-Pattern: "Known workaround. Bug closed."

If you've worked in Operations, you know how maddening it can be to deal with repeated "known issues." No matter how routine the response is, it still chews up your time with interruptions and toil. Dealing with repetitive problems may be frustrating. However, that frustration kicks into high gear when you submit a bug report on the issue — but Dev quickly closes it. The reason? It is usually something about not having the budget or priority. And besides, "Ops has a workaround."

TWL: John Hall on Swarming To Avoid the Painful 3-Tier Support Model

No matter which side of the trouble ticket you find yourself, I'm going to assume you hate the escalations, delays, and inevitable confusion. In this edition of Talks We Like, John Hall does a great job of proposing the Lean-inspired model of "Swarming" to avoid the pains of the traditional 3-tier support model (level 1, level 2, and level 3 responders).