A common debate in software development focuses on whether to use already-available tools or services, which offer better developer productivity, or stick with lower-level tools or custom-built solutions, which offer more control and potentially better performance and flexibility. This can be boiled down to the decision of whether to build or buy. These two approaches are at the root of many current tech industry ideological conflicts.
An old colleague of mine once said to me, “It doesn’t matter how inefficiently something DOESN’T work.” This was a joke used to make a point, so it stuck with me. It also made me consider that it does matter how efficiently something DOES work. Sometimes, when we have tools like Cribl Stream making things like routing, reducing, and transforming data so easy, we can forget that there might be a more efficient way to do it.
Lots of organizations are in a dilemma about which type of maintenance they should use in their business. In this blog, we will know what preventive maintenance and corrective maintenance are and what are the differences between them! So, without wasting any time, let us begin!
My first incident.io-incident happened in my second week here, when I screwed up the process for requesting extra Slack permissions, which made it impossible to install our app for a few minutes. This was a bit embarrassing, but also simple to resolve for someone more familiar with the process, and declaring an incident meant we got there in just a few minutes. Declaring the first incident when you start a new job can be intimidating, but it really shouldn’t be.
In their report titled “IT Resilience — 7 Tips for Improving Reliability, Tolerability and Disaster Recovery”, Gartner presents seven strategies for improving the resilience posture of your critical systems. These recommendations range from how to get started, to identifying IT hazards and risks to reliability, to capturing metrics and translating them into business value. In this blog, we’ll take a high-level look at the report and summarize some of its key findings.
Claiming that SaaS is the future is a broad statement until you take a second and look around you. Be it for your business or everyday needs, every problem has one or more SaaS solutions to solve them. People today are well aware of this growing reality that simpler, cheaper SaaS solutions are available all around them to make their lives easy.
What's the first small thing to do in o11y that would teach me something, bring something valuable, and open the way for something else? Observability doesn’t have to be a big, company-wide project. It can be useful locally and individually. A little playing around can get you some crucial insight into how your software works. Try it as a team, or in a pair, or by yourself. It takes 3 steps: Step 1 is easy. The other two might take ten minutes, or maybe more like a day.
Knowledge managers have an ongoing challenge: They want to encourage customers to self-serve and quickly find answers to their questions. They also want to minimize frustration if customers can’t quickly find an answer. Delivering great self-service is key to customer experience. It’s in everyone’s best interest if a customer doesn’t open a case (or incident). But where is the line between keeping your customer happy and causing undue delays?
