VictorOps

victorops

Who Owns the Incident Management Process?

When an incident strikes, the customer doesn’t care who solves the issue – they just want functional systems. So, organizations are constantly tasked with defining incident management processes and refining incident response plans. But, because every team and business is structured a little differently, a one-size-fits-all incident management process doesn’t make sense.

victorops

Best Practices for Contextualizing Incident Monitoring Data

As we all know, development practices in DevOps rely upon continuous feedback and constant analysis. This is done to ensure both the timely release of quality software and continuous improvement to the processes driving development. In many ways, these ideologies regarding analysis also hold true for bettering the incident management procedures employed by an organization. Incident management is crucial to delivering and maintaining quality software.

victorops

Automation of SQL Server Environments for SQL Developers

At any given time, a DevOps or DataOps team can be responsible for managing dozens of databases. With so much to monitor, automation is key for ensuring performance issues are recognized and addressed efficiently and quickly. To be sure, it can be daunting to hand off critical business operations to non-human operators (which is what happens when you automate database administration), but delivering repeatability and accuracy sometimes trumps gut feelings.

victorops

Developing On-Call Escalation Processes That Work

In a world of highly-integrated systems, microservices, cloud infrastructure and constant development, DevOps and IT teams are tasked with finding better ways to keep up with their own processes. By actively testing throughout the development lifecycle and preparing for incident response, you’ll build more resilient services up front while simultaneously being prepared when things go south.

victorops

Common DevOps Roles and Responsibilities

DevOps-oriented engineers live at the intersection of IT operations and software development – understanding much of what it takes to maintain IT infrastructure while also being able to write code and deploy new services. DevOps-minded teams not only create services – but they also maintain them. A DevOps structure forces teams to take accountability for their applications and infrastructure instead of allowing developers to throw code over the proverbial wall to IT operations.

victorops

Keys to Effective Release Management

Release management continues to change alongside the changing landscape of software development and IT operations. Microservices, serverless and containers are giving way to more complex, interconnected architecture. And, as continuous integration and continuous deployment (CI/CD) workflows become more common, releasing reliable services becomes more difficult. So, teams need to evolve their processes and tools to fit in with the modern world of agile release management.

victorops

The DevOps and IT Incident Response Plan

Rapid incident response in DevOps and IT can mean the difference between a 5-minute outage and a 5-hour outage. But, how you respond in real-time isn’t the only part of incident management and response. From alerting to post-incident reviews to communication methods, there are a number of ways you can make incident response more effective. And, one of those ways is to build a comprehensive incident response plan.

victorops

Enabling On-Call Developers to Succeed in a Shift-Left World

Over the past few years, the term shift-left has been gaining traction within DevOps organizations. Shift-left refers to a development approach where application quality and security become a focal point for the development team as early as possible in the development lifecycle. It’s implemented through strategies of end-to-end automated testing and continuous integration/deployment (CI/CD).