Operations | Monitoring | ITSM | DevOps | Cloud

A prelude to our upcoming six-part Observability Maturity Model Fundamentals blog series. By Lodewijk Bogaards At StackState, we have spent eight years in the monitoring and observability spaces. During this time, we have spoken with countless DevOps engineers, architects, SREs, heads of IT operations and CTOs, and we have heard the same struggles over and over.

Managing gas bills has a lot in common with managing cloud spend. In the summer, our gas bill increased with our summer adventures. Sitting home with the kids out of school and the warm summer months was not an option. Likewise, while discounts on gas certainly help, in reality they do not put much of a dent in the overall bill. The cheapest gallon of gas is still the one not used. If you’re a modern cloud-native business, you can’t just stop using the cloud.

It’s no secret that CI/CD pipelines make the lives of engineering and operations easier by accelerating the feedback loop for higher quality code and apps. They build code, run tests, and safely deploy new versions of your application. But just like any aspect of development, poor integration, invisible bottlenecks, and bugs can plague your pipelines. And debugging them? Well, it’s complicated.

With the growing complexity of IT environments, it is essential to have robust security processes that can safeguard IT environments from cyber threats. In this blog, we will explore how security operation centers (SOCs), help you monitor, identify and prevent cyber threats to safeguard your IT environments. This blog covers the following pointers.

The last few years have brought immense change in telco technology adoption trends, with the introduction of 5G, artificial intelligence (AI), the internet of things (IoT), cloud computing, and mobile edge computing.

We've all done it: "that'll be simple, I'll just write a quick script and..." In the case of calculating on-call pay, we really have done it before: our team have built the on-call pay scripts for several companies, and each attempt was a painful, error prone process. While we believe everyone on-call should be paid for their inconvenience, relying on someones side-project or back-of-napkin maths to calculate pay leads to mistakes, frustration, and wasted time.

I remember how excited I was to build my first Network Operations Center (NOC). It was a new idea at the time (yes, I know I’m dating myself), and boy, did we feel like we were cutting edge. The mere idea that we needed a place and a set of tools to monitor our entire infrastructure (because it’s never really been about just the network) was a big transition at the time. How things have changed.

At Civo we aim to provide users with the tools and knowledge to succeed in the cloud native landscape. So, we’re super excited to announce a brand new tech event, Civo Navigate! Whether you’re looking to join us in person or take part in the event, here’s your guide to all things Civo Navigate.

When it comes to starting your IoT project, organisations have a wider selection of connectivity options than ever before. In this blog, we consider which connectivity type might suit your IoT project best.

Running or operating applications requires several tasks throughout their lifecycle: scaling instances, checking the health, integrating with other applications, running backups, and applying updates – to name a few examples. It’s a time and labour-intensive process. To automate these tasks, developers can implement scripts for repeated execution. This is where the software operator comes in.