Let's talk bugs versus incidents
In this post, we’ll dig into the difference between a bug and an incident, why alignment on how they are defined matters, and how to ensure you’re still learning from the issue, even if it’s “just a bug.”
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
In this post, we’ll dig into the difference between a bug and an incident, why alignment on how they are defined matters, and how to ensure you’re still learning from the issue, even if it’s “just a bug.”
Want to try out Mattermost, but don’t have sufficient infrastructure or the time? Here is a guide on how to deploy Mattermost using minikube in five minutes.
Join Mark Boost, Dinesh Majrekar, and Saiyam Pathak to discuss the current state of the cloud industry and why costs are so high, how to take steps to reduce your spend, and looking at how Civo can help.
As we settle into the time of year when we reflect on what we're thankful for, we tend to focus on important basics such as health, family and friends. But on a professional level, IT operations (ITOps) practitioners are thankful to avoid disastrous outages that can cause confusion, frustration, lost revenue and damaged reputations. The very last thing ITOps, network operations center (NOC) or site reliability engineering (SRE) teams want while eating their turkey and enjoying time with family is to get paged about an outage. These can be extremely costly - $12,913 per minute, in fact, and up to $1.5 million per hour for larger organizations.
The DevOps pipeline is a crucial part of software development, but it can often get mired in bottlenecks. Most problems are caused by the development and operations teams having different responsibilities are due to inefficiencies in the pipeline design. However, thanks to continuous observability, DevOps now gets a new lease of life since it is possible to tweak the pipeline to suit the developer’s workflow.
Errors are part of building software. Even if you are one of the fabled 10X engineers, errors are still going to happen. When an error does occur, typically you are going to look at the stack trace to understand the why and who for triaging. But figuring out who to assign an issue to just based on the stack trace can be difficult. How many times do you see a stack trace in a Sentry issue, head to GitHub, and try to figure out who changed the line of code in question? Often would be our guess.