Operations | Monitoring | ITSM | DevOps | Cloud

Incident Management

The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.

Automating Common Diagnostics for Kubernetes, Linux, and other Common Components

This is the second piece in a series about automated diagnostics, a common use case for the PagerDuty Process Automation portfolio. In the last piece, we talked about the basics around automated diagnostics and how teams can use the solution to reduce escalations to specialists and empower responders to take action faster. In this blog, we’re going to talk about some basic diagnostics examples for components that are most relevant to our users.

What Is a Secure SDLC?

The Software Development Lifecycle (SDLC) framework defines the entire process required to plan, design, build, release, maintain and update software applications, including the final stages of replacing and decommissioning an application when needed. A Secure SDLC (SSDC) builds on this process, integrating security at all stages of the lifecycle. When migrating to DevSecOps (collaboration between Development, Security, and Operations teams), teams typically implement an SSDLC.

StatusCast Top Picks: 10 More Awesome Customer IT Status Pages

IT services are a critical backbone to the operations and functioning of most every business and organization. As more and more IT departments have embraced the need for good governance, this has driven greater transparency. From the perspective of IT service management, this has manifested itself as much greater openness when communicating about IT service availability.

Remote Actions for IT Remediation, IoT Actions and more

SIGNL4 supports the remote execution of automated tasks or workflows in IT or IoT systems using Remote Actions. These remote actions offer a wide range of applications. You can execute remote actions in response to an alert to trigger some kind of remediation action. But there are many more possible use cases. This article provides some examples and ideas about what is possible.

DevOps Tools

A tool that aids in automating the software development process is called DevOps Tool. It largely concentrates on interaction and cooperation between experts in product management, software development, and operations. A DevOps solution also enables teams to automate the majority of software development procedures including build, conflict management, dependency management, deployment, etc. and lessens human labour.

Cultural Adoption of Automation

You're convinced that automation of standard, basic tasks is the right way to go for your team. You want to get your teams """"out of the muck"""" and into more value-added tasks, such as the creation of new features, or launching new clients, or expansion into new territories. How do you build consensus with your teams? With your leadership? To convince your executive team that automation is the way to go, they'll insist on metrics to capture their return, whether through increased agility, improved service stability, and so on.

Incident Review & Postmortem Reports: 8 Best Practices

People make mistakes, technology breaks down, and processes aren’t infallible. But, when incidents happen, what can we do about it? What can we learn? As with all things, learning isn’t a binary action, it’s a process. And, when an incident occurs, organizations typically conduct a post-mortem analysis and generate a post-incident review to uncover what went wrong and why.

Sponsored Post

How to Spot the Effects of Alert Fatigue

Imagine being part of an overactive group chat that causes your phone to buzz every few minutes. In the beginning, you open every message but soon realize that most of them aren't important-or at least are not relevant to you. So, what do you do next? Maybe you let the messages pile up and check them later. Or perhaps, you mute the group chat and ignore the incoming messages altogether. You can blame this tendency to ignore or avoid incoming messages or notifications on one culprit: alert fatigue.

How Retrospective Data Enhances Reliability Insights

When things go wrong, we try to learn for the next time. Every incident should be a learning opportunity to make your system more reliable for the future. Luckily with Blameless Reliability Insights, you can see patterns in incidents at a glance, right out of the box. In fact, the ability to tag incidents makes reliability data even more helpful by allowing you to collect granular details about reliability, especially as they pertain to your unique business needs. ‍