We’re excited to announce that we’ve recently contributed Active Directory Domain Services (abbreviated Active Directory DS) monitoring support to the OpenTelemetry collector. You can check it out here! You can utilize this receiver in conjunction with any OTel collector: including the contrib collector, the observIQ’s distribution of the collector, as well as Google’s Ops Agent, as a few examples.

Node.js is an established platform for developing server-side applications in JavaScript. One of the most fundamental concerns that arise during the development of Node.js apps is how to carry out proper logging that will be safe, secure and performant. While there are several options for configuring Node.js logging, a few specific engineering best practices still apply, no matter which option you choose.

We are pleased to announce we have closed our Series D round of funding, led by Tiger Global with participation from existing investors IVP, CRV, Redpoint Ventures, Sequoia, and Greylock Partners. In this round, we raised $150M, bringing our total raised to over $400M. This new fundraising round further validates the value we provide to customers.

Many CXOs believe that Web3 will power the next paradigm shift and transform the world. As a result, they are accelerating their learning curve to spot opportunities and leapfrog to next-gen business models that will catapult their organizations to new heights. But is there really an urgency to explore what Web3 can offer?

NGINX is one of the most widely used reverse proxy servers, web servers, and load balancers. It has capabilities like TLS offloading, can do health checks for backends, and offers support for HTTP2, gRPC, WebSocket, and most TCP-based protocols. When running a tool like NGINX, which generally sits in front of your applications, it’s important to understand how to debug issues. And because you need to see the logs, you have to understand the different NGINX logging mechanisms.

As CEO of Cribl, one of my greatest privileges is to spend time on the road and on calls with our customers hearing about their needs and challenges. Cribl is a focused company. We build software for observability and security. With this lens, it becomes clear the industry is neglecting to address the unique needs of our users. There are many reasons, most of which are simply that vendors tend to come at a user’s problem through the lens of their existing technology.

For the next interview in our series speaking to technology specialists from around the world, we’ve welcomed experienced CTO, Leonard Trigg. Leonard is a member of the Harbourfront executive management team and serves as the firm's Chief Technology Officer. Joining the industry in 1995 Leonard has a background in enterprise technology, finance and operations. Leonard previously served as the Chief Operating Officer and Director at Vertex One Asset Management Inc.

Today, we are excited to announce that the MySQL integration has received an important update, which includes a new pre-built MySQL logs dashboard and the Grafana Agent configuration to view and collect MySQL server logs. The integration is already available in Grafana Cloud, our platform that brings together all your metrics, logs, and traces with Grafana for full-stack observability.

Today we’re excited to introduce Mezmo: our new name and brand that represents the future of observability.

“We lost choice and control when we migrated to Splunk Cloud, but got it back when we adopted Cribl Stream.” The above quote is from a new Cribl customer talking about why they adopted Cribl Stream to manage observability and security data.