How is your organization handling Kubernetes observability? What tools are you using to monitor Kubernetes? Is it a time-consuming, manual process to collect, store and visualize your logging, metrics and tracing data? And, what are you actually getting out of all that investment? At Logz.io we’re trying to make this process easier for customers who are serious about Kubernetes observability. We’ve made significant investments in this area for Kubernetes use cases.

If you’ve been around the observability world for the past few years, you’ve probably heard a few stats around data growth. Worldwide, data is increasing at a 23% compound annual growth rate (CAGR), per IDC. That means in five years, organizations will be dealing with nearly three times the amount of data they have today – generated by diverse and emerging sources, from data centers to cloud sources to edge computing.

If you’ve ever seen Indiana Jones and the Last Crusade, you might remember the scene where Indy and his dad are in a room replete with the most ornate chalices possible, only to realize that the Holy Grail is the most plain, utilitarian one in the room. Windows event logs are the IT version of the plain-looking clay cup that holds the key to answering your service questions and system issues.

The UK Government’s G-Cloud-13 framework is live, with loads of new services available to UK organisations. Discover Aiven’s offering here!

NestJS is a popular framework for Node.js that allows you to build efficient and scalable backend applications. With AppSignal, you can monitor your NestJS app with ease and rely on OpenTelemetry to handle third-party instrumentations. AppSignal even provides helper functions to help you build comprehensive custom instrumentations. This article aims to help you get the most out of your AppSignal integration.

Very early in my career, a mentor taught me an extremely important lesson: “There is no substitute for talking to your customers.” No market research, focus groups, or surveys can take the place of getting face to face with your customers and having an honest conversation.

Agencies have taken a siloed approach to deploying technology solutions to meet government digitization and modernization goals. Although this allows them to roll out rich digital experiences for citizens and employees, it’s not a scalable method—nor is it effective in terms of cost and resources. Like many agencies, the U.S. Department of Labor (DOL) had several key platforms in place to drive its digitization efforts, but the management of these platforms lacked centralization.

When it comes to cloud costs, engineers have a particular reputation. The executive suite and finance department often share perplexing frustration about why engineers appear not to care about budgets and costs at all. They provide hard budget limits, yet engineers frequently surpass them, citing performance and user experience as reasons for the excess spending.

Building digital platforms, and platform engineering teams to support them, isn’t new. The platform approach first emerged more than 20 years ago and predates the DevOps movement that began in the mid-2000s. But the recent surge in popularity of platform engineering has caused some to argue that “DevOps is dead” and modern platform engineering has replaced it. Here’s what we found in the 2023 State of DevOps Report to counter that argument.

Scottish essayist Thomas Carlyle may not have been thinking about remote working tools for software development teams when he wrote, “Man is a tool-using animal. Without tools, he is nothing; with tools, he is all”. However, the statement is apt in this age of the internet with hundreds of thousands now working from remote locations. The statement is especially true for team leaders charged with the herculean task of managing remote software development teams.