Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

Managing an Elasticsearch cluster can be complex, costly, and time-consuming - especially for large organizations that need to index and analyze log data at scale. In this short guide, we’ll walk you through the process of creating an Amazon S3 bucket, configuring an IAM role that can write into that bucket, and attaching that IAM role to your Amazon S3 instance - all using the AWS Command Line Interface (CLI).