Operations | Monitoring | ITSM | DevOps | Cloud

After many weeks of work, we're delighted to announce the latest feature of the incident.io platform: Workflows. Configure your processes once, and we'll make sure you follow them, every time ✨ A little while ago, I was asked the question: “what makes a good incident response?”. Whilst there’s infinite nuance in the answer, mine was pretty straightforward. The best incidents are founded on principles of communication, coordination, and clear roles and responsibilities.

Systems and platforms continue to grow more complex and distributed. The march towards distributed microservices has been accelerated with Kubernetes; arm yourself with a Kubernetes manifest and up your replica count and like magic, you have more than one endpoint for your workload. In the Kubernetes ecosystem, there has been a lot of investment on the infrastructure side of the house for example in making sure clusters are performant and have the ability to scale.

Technology is one of the main success factors for any organisation. A few decades ago, when technology (and life) were not as fast-paced as today, IT was more about keeping the lights on and maintaining business as usual operations. Today, the game has massively changed. On the roads that are ever-changing, innovation is what keeps the wheel spinning. If you think that the world is doing enough innovation today, then it would be very interesting to check the recent Growth & Innovation McKinsey report.

‍Joe Karlsson is a senior developer advocate at SingleStore. SingleStore has a highly scalable SQL database that delivers maximum performance for transactional and analytical workloads, all with familiar relational data structures. Joe collaborates with teams across the company to amplify developers' voices and provide support for multiple audiences. Today, we're going to talk about cross team empathy and why DevRel and DevOps work hand in hand.

How many times have you been aware of an error or performance issue, but lacked the ability to quickly uncover the root cause and determine why it happened in the first place? One of the most powerful ways to do this is by surfacing code-level insights right where you need them, alongside the context needed to take action. By using our latest integration with Azure Repos, you’ll be able to get to the ‘why’ of issues, faster – all directly within Raygun.

We’re excited to announce the launch of private network integrations! This lets you use our existing Status Checks and Webhooks features on systems residing inside of your internal network, empowering any Gremlin team to automate Gremlin tasks safely and securely.

Infrastructure as Code tools like Terraform provides greater support for automation, especially when dealing with multiple resources in a complex cloud infrastructure. In this blog, learn how Terraform can make your life simple by launching multiple instances in one-go. If you are new to Amazon AWS and need to create or launch multiple resources in one go, then nothing is better than using Terraform count. The Terraform count argument allows you to launch as many resources as you wish, of the same kind.

Welcome back to another iteration of “Build Things on Purpose” where we talk with developers and engineers who are creating tools that help us build more reliable systems. Today Itiel Shwartz, CTO and Co-Founder of Komodor, has joined us to chat about what they’re doing to help tame the chaos of Kubernetes. Itiel talks about Komodor’s goal of making troubleshooting Kubernetes not only easy, but potentially even fun!