Operations | Monitoring | ITSM | DevOps | Cloud

We’re creating a new way to install and set up Sentry. Starting with Next.js, you’ll be able to set up new Sentry accounts or create new Sentry Next.js projects via the terminal and running a single command. Getting started is simple(r). While you can still visit sentry.io/signup to create an account or create a project from within the app – now you can skip all the clicks, navigate to your repo and run this command.

Have you heard about traces? Most likely, yes! Do you confuse it with auditing? Hope not. Today, we're going to talk about tracing, specifically “Distributed Tracing,” and do a deep dive into it. Once we’re familiar with distributed tracing, we will show you how to implement it with OpenTelemetry - a new-age observability framework.

Our development teams continue to improve Progress Flowmon. The latest update takes the core Flowmon product to version 12.2, while our industry-leading Anomaly Detection System (ADS) gets incremented to ADS 12.1.

Many organizations rely on distributed tracing in Datadog APM to gain end-to-end visibility into the performance of their Kubernetes applications. But as teams grow, it can become impractical for them to manually configure each new application with the libraries and environment variables needed for tracing.

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.

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.

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.

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.

In modern application development and architecture, there has been a big push from monolithic, large applications that can do everything a product would need, to many smaller services that have a specific purpose. This onset has brought on the age of microservice frameworks (micro-frameworks), with the goal of making it easier to prototype, build, and design applications in this paradigm.

Five worthy reads is a regular column on five noteworthy items we have discovered while researching trending and timeless topics. This week, we explore the impending impact of the metaverse on the future (or now) of work and productivity. Illustration by Akshaya Maheswaran Imagine a world where you can work from anywhere, collaborate with colleagues from around the globe, and attend meetings in virtual reality (VR) conference rooms.