Operations | Monitoring | ITSM | DevOps | Cloud

A short history of software monitoring, from the 00s. What has changed? Why are things so arcane?

In today’s digital age, the ability to collaborate effectively and manage documents efficiently is more critical than ever. Enter SharePoint Online, a powerful cloud-based platform by Microsoft that is revolutionizing the way organizations operate. It’s more than just a tool; it’s a game-changer in the realm of digital collaboration and content management.

At Obkio, our mission is to provide comprehensive network monitoring and troubleshooting solutions tailored specifically for MSPs (Managed Service Providers), ensuring the proper functioning of their networks and services for their clients. MSPs are a big part of our client base and we've had the chance to chat with numerous business owners and network admins to really get to the core of their needs. Why?

Carmakers are facing numerous challenges on the path towards software-defined vehicles (SDVs), such as legacy vendor dependence, which is leading to a lack of scalability, and high maintenance costs. Adopting a software-centric approach should reduce complexity and costs, accelerate time to market, improve product quality, increase flexibility, and provide more robust cybersecurity.

The FinOps Foundation sets out six FinOps principles cloud-based companies should follow to achieve and maintain optimal control over their cloud spending and cost efficiency. On the surface, they seem straightforward enough. The first principle, for example, is that teams should always collaborate in real-time to “continuously improve for efficiency and innovation” when it comes to staying on top of software development cloud costs.

In the initial stage of the digital era, only a few businesses were using digital tools and technologies to enhance their performance and efficiency. But now, things have changed and almost 90% of businesses use top-rated technologies to stand out from their competitors. In fact, some of them rely heavily on robust IT infrastructure for seamless delivery of quality service and applications. As a result, infrastructure is becoming more complex and open to threats.

For Android developers, test automation on CI/CD platforms such as CircleCI has become an indispensable part of the development workflow. But merely implementing automated testing is no longer enough to remain competitive and continue to develop at speed. Developers must also work to continuously monitor, maintain, and improve their test automation. As an application grows in complexity, the scale of development grows, as does the number of automated tests.

In November 2023 we discovered an issue in the Go standard library’s net/http.Client that allowed an attacker who controls redirect targets on a server to exfiltrate authentication secrets. Soon after, we discovered a similar issue in net/http/cookiejar.Jar. The issues, collectively designated CVE-2023-45289, have now been fixed in Go 1.22.1 and Go 1.21.8, released on March 5, 2024. This blog post dives into the technical details behind those two bugs and the patch that addresses them.

Managing web applications from the ground up can be a daunting task. One application alone can quickly grow in complexity, let alone the multiple applications that are often required by different business units and stakeholders growing simultaneously. Add the ever-changing landscape of trendy frameworks and runtimes, and you quickly find yourself with an unmanageable mess of different technologies. Standardizing your application stack can help reduce the clutter.