In technology, having “modern” capabilities is standard. Staying ahead of the curve is critical, and keeping outdated technology or processes going can be a recipe for disaster in a complex, ever-changing landscape. Ensuring the smooth functioning and performance of software systems is paramount. This is where modern observability—a sophisticated approach to monitoring and understanding the inner workings of applications and infrastructure—is required.

The main objective of the ELK (Elasticsearch, Logstash, and Kibana) is to aggregate logs. However, with the increased usage of ELK and Kubernetes as a pairing the solution can go beyond the aggregation of standard logs and include monitoring and analysis of Kubernetes telemetry data. Therefore, more users are looking at deploying the ELK stack on Kubernetes. Yet, deploying the ELK stack on Kubernetes can be a complex task but with the assistance of Helm charts, the process is much simpler.

As Elastic continues its commitment to OpenTelemetry (OTel), we are excited to announce the Elastic distribution of the OTel Java Agent. In this blog post, we will explore the rationale behind our unique distribution, detailing the powerful additional features it brings to the table. We will provide an overview of how these enhancements can be utilized with our distribution, the standard OTel SDK, or the vanilla OTel Java agent.

This is the second 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 first and last posts, you can find it here. In the dynamic world of managing observability and telemetry data, pricing models for tools and platforms are showing their age, creating a significant disconnect between vendors and the IT and security teams they serve.

When sending data to Google Cloud, like logs, metrics, or traces, it can be beneficial to split the data up across multiple projects. This division may be necessary since each team has its own project, a central project is used for security audit logs, or for any other reason that your organization has. BindPlane has effective tools to manage this process. In this walkthrough, we will add fields to telemetry entries, allowing us to associate entries with a specific project and properly route them.