We are delighted to announce the alpha release of the Elastic OpenTelemetry Distribution for Node.js. This distribution is a light wrapper around the OpenTelemetry Node.js SDK that makes it easier to get started using OpenTelemetry to observe your Node.js applications.

Here at Mezmo, we see the purpose of a telemetry pipeline is to help ingest, profile, transform, and route data to control costs and drive actionability. There are many ways to do that as we’ve previously discussed in our blogs, but today I’m going to talk about real-time alerting on data in motion, yes - on streaming data, before it reaches its destination.

We are excited to announce the release of Graylog 6.0, which brings updates across our entire product line!

Before we start, I have a confession: I absolutely love Digg (people are still Digging things, right?) errr...Reddit. It actually is my front page to the internet, where I research upgrades for my home lab/VR/other niche hobbies, watch silly videos, ingest low-effort memes, judge if people are ‘AHs’ or not on /r/amitheasshole, and occasionally talk trash to other Redditors about my Michigan-based sports teams.

A healthy relationship between services and databases is fundamental to overall application performance. Unchecked database issues can compromise application efficiency, user experience, and ultimately, your organization’s bottom line. To steer clear of these consequences, monitoring your databases should be a key component of your observability—and with the launch of Coralogix Database Monitoring, it can be.

Everyone loves managed services until the bill comes in. High performance search indexers are a premium technology and have premium resource requirements. Graylog 6.0 introduces Data Tiering to put the management back in centralized data management.

The ELK (Elasticsearch, Logstash, and Kibana) stack’s main objective is to aggregate logs, but the vastly popular open-source project has numerous uses alongside aggregating logs. ELK can easily integrate with Kubernetes and is a common solution that enables users to gather, store, and examine Kubernetes telemetry data. However, with the continual rise of micro-service architecture, users are searching for an improved method of aggregating and searching through logs for debugging purposes.

This is the first in a series of blog posts about the disconnect between modern IT and security teams and the vendors they’re forced to work with. If you’re looking for the second and third posts, you can find them here and here. Imagine this scenario: You’re grappling with the ever-escalating costs of your legacy solutions. What’s the logical next step? For many, it’s exploring the new wave of tools emerging, such as data warehouses.

As the cybersecurity landscape becomes more and more complex. It seems like we hear about a major breach of a different company every day. Enterprises are looking for robust solutions to help them manage the surge in data and security incidents. That’s why our recent collaboration announcement with Microsoft means so much to us. It’s not just a piece of paper; it’s a testament to our dedication to providing customers with the best tools and solutions for the job.

Redis, which stands for remote dictionary server, is an open-source, in-memory data structure store that is commonly used as a database, cache, and message broker. Utilizing Redis provides numerous benefits for your team and organization, which have helped drive the tool's increase in popularity. A key example of this is speed, Redis works primarily in memory, making it particularly fast for data operations.