Prometheus·2yAnnouncing Prometheus 3.0
Prometheus 3.0 is now available, marking the first major release in seven years. Key updates include a new UI, Remote Write 2.0, UTF-8 support, and enhanced interoperability with OpenTelemetry. Native histograms are introduced as an experimental feature. The release also includes some breaking changes, so users are encouraged to review the migration guide. Performance improvements and upcoming features were also highlighted.
Grafana Labs·2yPrometheus 3.0 and OpenTelemetry: a practical guide to storing and querying OTel data
Prometheus 3.0 aims to improve integration with OpenTelemetry by addressing challenges such as resource attributes, UTF-8 support, and temporalities. The Prometheus 3.0 release includes features like promoting resource attributes to metric labels, a new `info` PromQL function, and stable OTLP support for easier data ingestion and querying. Users can also utilize the delta to cumulative processor in OTel Collector for better data handling. Future developments will focus on enhancing interoperability and scalability.
Hacker News·2yhyperdxio/hyperdx at v2
HyperDX enables engineers to debug production issues quickly by offering an easy way to search and visualize logs and traces on any Clickhouse cluster. It supports schema-agnostic setups, offers blazing-fast searches, intuitive full-text and property search, and native JSON querying. HyperDX is compatible with OpenTelemetry and supports multiple programming languages and platforms. It is available in beta for local use and as a hosted cloud service. HyperDX aims to simplify observability and mitigate the shortcomings of existing tools by being cost-effective, user-friendly, and integrative.
Last9·2yKubernetes Observability with OpenTelemetry Operator
The OpenTelemetry Operator enhances observability in Kubernetes clusters by simplifying the deployment and management of telemetry pipelines. It automates tasks such as scaling collectors, exporting telemetry data, and instrumentation. Key features include various deployment modes, custom pipelines, scalability, and auto-instrumentation. Best practices involve starting small, using CRDs for configurations, monitoring collector health, isolating telemetry pipelines by namespaces, and using metrics for scaling.
AWS Fundamentals·2yOpenTelemetry on AWS: Observability at Scale with Open-Source
Learn how to implement an observability stack on AWS using OpenTelemetry, CloudWatch, and AWS X-Ray for serverless applications. This guide walks through configuring AWS Lambda for trace and log collection, and how the AWS Distro for OpenTelemetry provides a secure, production-ready solution for instrumenting applications with minimal code changes.
Grafana Labs·1yHow to use OpenTelemetry and Grafana Alloy to convert delta to cumulative at scale
Migrating to a Prometheus-based ecosystem with Grafana Alloy, which integrates OpenTelemetry, makes handling metrics easier, especially when converting delta metrics to cumulative ones. This post details the algorithm used for this conversion and outlines the load balancing and container setup necessary for scalable deployment. It also mentions recent updates to the OpenTelemetry Collector, making the process more efficient and scalable.
OpenTelemetry·2yOpenTelemetry Java Metrics Performance Comparison
OpenTelemetry aims to provide a universal observability standard, offering tools for traces, metrics, and logs across various languages. This post zooms in on the performance of the OpenTelemetry Java metrics SDK, especially focusing on the crucial aspects of recording and exporting metrics. By aggregating measurements, this system reduces data footprint while maintaining performance. The post also benchmarks OpenTelemetry Java against Micrometer and Prometheus, showcasing its superior memory allocation efficiency during metrics collection and export, particularly when attributes are not known ahead of time.
Baeldung·1yWorking With OpenTelemetry Collector
Learn how to utilize the OpenTelemetry Collector to gather, process, and export telemetry data from your applications. This guide covers setting up an OpenTelemetry Collector using Docker, implementing both automatic and manual instrumentation in Java, and configuring the collector for effective data processing and exporting to various backends like Prometheus and Jaeger. Additionally, it explores enhancing the collector's capabilities through extensions such as zPages.
OpenTelemetry·2yPrometheus and OpenTelemetry - Better Together
Prometheus and OpenTelemetry (OTel) are key tools for monitoring complex distributed systems. While OTel focuses on instrumentation without offering backend storage, Prometheus provides a time-series data store and a web interface for visualizing metrics. The integration of OTel with Prometheus, particularly in Kubernetes environments, is explored. The OTel Collector’s Prometheus Receiver ingests Prometheus metrics, and the Target Allocator aids in Prometheus service discovery and ensures even distribution of targets among collectors. This setup removes the need for maintaining Prometheus as a data store and provides flexibility in monitoring Kubernetes systems using OTel tools.