Welcome to the second installment in our series on OpenTelemetry naming best practices. In our previous post, we explored how to name spans using the {verb} {object} pattern. Today, we’re diving into span attributes—the rich contextual data that transforms your traces from simple operation logs into powerful debugging and analysis tools. This guide targets developers who are: Instrumenting their own applications with custom spans and attributes Enriching telemetry beyond what auto-instrum...| Blog on OpenTelemetry
Did you know that OpenTelemetry has had more than 23,000 contributors—that’s individuals who shared issues, commits, pull requests, or comments on GitHub—since the project started? We always encourage everyone to get involved, whether that’s by joining one of our (many!) CNCF Slack channels, or dropping into any public meeting to listen in and share different perspectives. This openness is one of our greatest strengths, but it also means we get a firehose of feedback via many differen...| OpenTelemetry
One of the most fundamental yet often overlooked aspects of good instrumentation is naming. This post is the first in a series dedicated to the art and science of naming things in OpenTelemetry. We’ll start with spans, the building blocks of a distributed trace, and give you the most important takeaway right at the beginning: how to name the spans that describe your unique business logic. Naming your business spans While OpenTelemetry’s automatic instrumentation is fantastic for covering ...| Blog on OpenTelemetry
In the latest session of OTel in Practice, engineers Huxing Zhang and Steve Rao shared Alibaba’s journey adopting OpenTelemetry within their services. The discussion focused on a wide range of topics, from Java agents to Go compile-time instrumentation, and of course Gen-AI observability! Focusing on Java, Alibaba initially used an in-house solution based on Pinpoint, but faced limitations with framework support and asynchronous context propagation. It was then that they decided to migrate ...| OpenTelemetry
On May 29th, 2025, I wrapped up my mentorship with Prometheus through the Linux Foundation Mentorship Program. My project focused on understanding how Prometheus handles OpenTelemetry resource attributes and how that experience could be improved for users. My job was to conduct user research to get the user perspective on this challenge. In three months, I conducted user and stakeholder interviews, ran a survey, and analyzed the findings. In this article, I’ll share how I conducted the rese...| OpenTelemetry
TL;DR OpenTelemetry Weaver helps teams build observability by design, enabling consistent, type-safe, and automated telemetry through semantic conventions. With Weaver, you can define, validate, and evolve your telemetry schemas, ensuring reliability and clarity across your systems. Why consistency matters: Enter semantic conventions Have you ever experienced… A deployment that breaks existing alerts or dashboards because a metric name changed? Writing overly complex queries because teams u...| Blog on OpenTelemetry
As OpenTelemetry adoption grows across infrastructure and application layers, easing the operational burden of instrumentation remains a shared priority. Today, we’re excited to highlight a recent donation from Splunk to the OpenTelemetry community: a host-based mechanism to automatically inject OpenTelemetry Automatic Instrumentation into your app on any Linux host. This component has reached production stability and is now being donated to the community as the OpenTelemetry Injector. It h...| OpenTelemetry
Yesterday the Cloud Native Computing Foundation (CNCF) announced that CNCF Slack workspace will be converted from an enterprise plan to a free plan on Friday, June 20, 2025. This will have implications for how Slack works for the OpenTelemetry community, including a few limitations that we will need to be aware of; however, we don’t anticipate this change to radically impact our collaboration. Although there will be no disruption to OpenTelemetry’s access to the Slack workspace, all users...| Blog on OpenTelemetry
OpenTelemetry, like all open source projects, only exists thanks to the tireless work of thousands of contributors and maintainers. To celebrate and recognize Pride Month in the United States, we’ve created several variants of our iconic telescope logo for contributors to use. Happy Pride! You can download the files here.| Blog on OpenTelemetry
On June 26, 2025, OTel Community Day and Open Observability Summit are joining forces at Open Source Summit North America. The OpenTelemetry governance and technical committees, along with project maintainers, are excited to present two community-led tracks, one co-located event, and a shared goal: bring the observability community together to collaborate, learn, and shape the future of open source observability. Open Observability Summit is for developers, operators, and technical leaders wh...| Blog on OpenTelemetry
The OpenTelemetry Contributor Experience SIG recently surveyed the community to learn what it’s like to contribute to the project and what we can do to improve the contributor experience. The Contributor Experience Survey asked contributors for their thoughts about the project’s organization, SIG contributions, leadership committee interactions, and event attendance. We received 120 responses and heard from all 47 Special Interest Groups (SIGs). We’ll use this feedback to make contribut...| OpenTelemetry
The goal of this blog post is to demonstrate how you can expose an OpenTelemetry (OTel) Collector running inside Kubernetes to the outside world securely, using the Kubernetes Gateway API and mutual TLS (mTLS) for authentication and encryption. As observability becomes increasingly critical in modern distributed systems, centralizing telemetry data via OTel Collectors deployed in one or many Kubernetes clusters is common practice. Often, services or agents running outside your Kubernetes clus...| Blog on OpenTelemetry
The Semantic Conventions SIG is excited to kick off the RPC stabilization effort! Following the stabilization of the database conventions in May 2025, we’re continuing our work to stabilize key areas—and RPC is next. It takes a village to define a solid convention, especially for a space as diverse as RPC technologies, which include gRPC, JSON-RPC, Apache Dubbo, and many others. If you work on one of these frameworks, use them extensively, or are simply interested in learning more, come j...| Blog on OpenTelemetry
The OpenTelemetry Collector’s kubeletstats receiver is a crucial component for collecting Kubernetes node, pod and container metrics. To improve metric accuracy and adhere to OpenTelemetry semantic conventions, we are updating how CPU metrics are named and emitted. This blog post explains the motivation behind this change, the impact on users, the role of the feature gate which was introduced for this change, and guidance on migrating. Why This Change? Historically, the kubeletstats receive...| Blog on OpenTelemetry
The OpenTelemetry project invites you to join members of the OpenTelemetry community at KubeCon + CloudNativeCon Japan (registration) and at the co-located Community Day in Tokyo from June 15 to 17, 2025. This post covers all currently scheduled activities related to OpenTelemetry that are happening during KubeCon. Check back for updates before the start of the conference! Community Day Taking place on June 15, this free event offers a chance to engage with the cloud native community before t...| OpenTelemetry
The OpenTelemetry project invites you to join members of the OpenTelemetry community at KubeCon + CloudNativeCon China (registration) in Hong Kong from June 10 to 11, 2025. This post covers all currently scheduled activities related to OpenTelemetry that are happening during KubeCon. Check back for updates before the start of the conference! KubeCon talks and maintainer sessions Antipatterns in Observability: Lessons Learned and How OpenTelemetry Solves Them by Steve Flanders, Splunk Tuesday,...| Blog on OpenTelemetry
We are excited to announce the next phase of the OpenTelemetry Protocol with Apache Arrow project (OTel-Arrow). We began this project several years ago with the goal of bridging between OpenTelemetry data and the Apache Arrow ecosystem. Apache Arrow is a framework designed for zero-copy exchange of structured data between column-oriented data producers and consumers. We believe that having OpenTelemetry data accessible to external systems through Apache Arrow will lead to powerful integration...| Blog on OpenTelemetry
We’re back with our fourth edition of Humans of OpenTelemetry, this time from KubeCon EU in London, UK. Once again, Reese Lee and I interviewed OpenTelemetry contributors and end users, and learned how they got involved with OTel: Marylia Gutierrez (Grafana Labs) Adriel Perkins (Liatrio) Hanson Ho (Embrace) Jamie Danielson (Honeycomb.io) Mikko Viitanen (Dynatrace) Damien Mathieu (Elastic) Jacob Aronoff (Omlet) Alolita Sharma (Apple) Also, special thanks to: Reese Lee, my co-interviewer Henr...| OpenTelemetry
If you’ve been following OpenTelemetry for a while, you’ve probably heard a lot about logs. Log bridges, Logs API, events, you name it, we’ve talked about it. This blog post is intended to be a discussion of the rationale and current design direction of logging in OpenTelemetry. Definitions Let’s get started with a basic definition of how OpenTelemetry thinks about logs. Broadly, logs are any telemetry that is emitted through a log pipeline, and are created by calling the Logs API. Th...| OpenTelemetry
The OpenTelemetry Developer Experience SIG recently surveyed the community to better understand where the SIG could have the most impact on improving the developer experience. We received 218 responses, which we will use to guide our prioritization of work within the SIG. This post summarizes our findings and where we will focus in the near term. Thank you to all those who participated in the survey! If you are interested in joining us in these efforts or providing additional insights on wher...| OpenTelemetry
OpenTelemetry (OTel) is often touted as the future of observability, promising vendor neutrality and comprehensive data collection. But what’s the reality for those who use it daily? We sat down with several engineers and SREs to get their unfiltered thoughts on OTel. The result? A candid conversation about the good, the bad, and the sometimes frustrating aspects of working with OTel. In preparation for the KubeCon talk OTel Sucks (But Also Rocks!), Juraci spoke with community members and g...| Blog on OpenTelemetry
Hello world! I’m Richard Chukwu, a Computer Engineering graduate from the University of Benin, Nigeria. My journey into tech has been fueled by a blend of curiosity and an unwavering commitment to growth. These are the pillars that not only uphold my personal values but also form the foundation of my professional aspirations. I still remember the nervous excitement I felt when I received the email confirming my selection for Outreachy. It was a moment of validation, but also one filled with...| OpenTelemetry
2025: Year of AI agents AI Agents are becoming the next big leap in artificial intelligence in 2025. From autonomous workflows to intelligent decision making, AI Agents will power numerous applications across industries. However, with this evolution comes the critical need for AI agent observability, especially when scaling these agents to meet enterprise needs. Without proper monitoring, tracing, and logging mechanisms, diagnosing issues, improving efficiency, and ensuring reliability in AI ...| OpenTelemetry
TL;DR Take our OpenTelemetry Contributor Survey and help us enhance the contributor experience. We appreciate your time and feedback! Since its founding, OpenTelemetry has had thousands of contributors from around the world, including end users, vendors, and students. Last summer some members of the OpenTelemetry project came together to create the Contributor Experience SIG, which is focused on ensuring that contributors of all types have a great experience with the OpenTelemetry project. Si...| OpenTelemetry
The OpenTelemetry project and The Open Mainframe Project established the SIG “OpenTelemetry on Mainframe” at the beginning of 2024. Our focus is to enable OpenTelemetry on the mainframe for improved end-to-end observability and to support mainframe participation in hybrid cloud applications. The SIG launched a new survey that calls for your participation. Background While there are many definitions of observability, we will refer here to the ability to receive actionable insight about the...| OpenTelemetry
The OpenTelemetry community is excited to announce the beta release of the OpenTelemetry Go Auto-Instrumentation project! This milestone brings us closer to our mission of making observability simple, accessible, and effective for Go applications. What is Go Auto-Instrumentation? OpenTelemetry Go Auto-Instrumentation allows developers to collect traces from their Go applications without requiring manual code modifications or rebuilding binaries. By dynamically instrumenting applications at ru...| OpenTelemetry
Standards are only useful if they’re widely adopted, and adoption is only effective if the available tooling facilitates it. I imagine SI units would not have been too popular when they were introduced if you had to build your own scales to weigh things in Kilograms! If you use OpenTelemetry in Go, you’ll be familiar with the challenges of configuring instrumentation libraries to automatically generate telemetry from well-known open source components. Due to the compiled nature of the lan...| OpenTelemetry
What a year it has been for OpenTelemetry! The OTel Demo turned 1, the OpenTelemetry project announced general availability of the OpenTelemetry specification, Trace-Based Testing was added to the OTel Demo, we saw some exciting OTel integrations, and let’s not forget how we had not one, but TWO Observability Days in 2023 - one for KubeCon Europe in Amsterdam, and one for KubeCon North America in Chicago. Those are only a few of the highlights! Many more were featured in past releases of Op...| OpenTelemetry
The OpenTelemetry Java agent is a convenient and well-established way to instrument Java applications. However, as of today it is not possible to use it with GraalVM Native Images. To provide you with an easy and seamless way for Spring Boot Native Image application nevertheless, the OpenTelemetry Java contributors have improved the existing OpenTelemetry Spring Boot Starter to work well with Spring Boot Native Image applications. Read on to learn more! A history of the last months The OpenTe...| OpenTelemetry
While OpenTelemetry (OTel) is here to help you with troubleshooting and handling the “unknown unknowns”, it is also instrumental for managing route tasks like monitoring system metrics, like disk usage, server availability or SSL certificate expiration dates. This can be achieved by utilizing any one of the 90+ receivers available for the OpenTelemetry Collector, such as the Host Metrics Receiver or the HTTP Check Receiver. But what if the available receivers don’t meet your specific ne...| OpenTelemetry
As more and more users are looking to use OpenTelemetry instrumentation in their production deployments, one important consideration is the impact that OpenTelemetry will have on their application performance. In this blog post I will discuss a few recent improvements in tooling around performance benchmarking. Measuring performance overhead Instrumentation is not free. It intercepts an application’s operations and collects (often) a large amount of data, which takes additional CPU and memo...| OpenTelemetry
In the following, we will walk through how to do logs collection with OpenTelemetry (OTel). To keep things simple, we will use Python as the demonstration programming language, however note that at time of writing the logs support there is still early days so things might need some updating. We will show the evolution from using print statements for logging (Baby Grogu level) to logging to a file along with the OpenTelemetry Collector (Expert Grogu level) to using the OTel logs bridge API to ...| OpenTelemetry
OTel integration! A no-brainer integration: Adding OpenTelemetry support to the Otterize network mapper Otterize automates workload Identity and Access Management (IAM) for zero-trust, automating policies like Kubernetes network policies, Istio policies, AWS IAM policies, and more, through a collection of open source projects. To enable that automation, Otterize built the network mapper. Otterize network mapper is a standalone Kubernetes tool that builds a live network map of your infrastruct...| OpenTelemetry
We are thrilled to unveil the OpenTelemetry Protocol with Apache Arrow, which is based on Apache Arrow, a columnar-oriented memory format used for developing analytics applications. This integration facilitates a reduction in telemetry data traffic by a factor of 10 after compression, offering a 40% improvement over the best existing OpenTelemetry Protocol (OTLP) configurations with Zstandard (zstd) compression enabled. As a result, this new protocol emerges as an optimal choice for transport...| OpenTelemetry
This year marked many milestones for the OpenTelemetry project. The project achieved the goals it had set in 2019 by announcing the general availability of of the logging signal, the last of the signals it had originally committed to. In addition, the project continued to grow the number of contributors, being the second most active project in the CNCF for a second year in a row, behind Kubernetes.| OpenTelemetry
OTel integration! Cloud Foundry recently integrated the OpenTelemetry Collector for metrics egress and we learned a lot along the way. We’re excited about what the integration offers today and all the possibilities it opens up for us. What we were looking for Cloud Foundry is a large multi-tenant platform as a service that runs 12-factor applications. Cloud Foundry platform engineering teams usually run 4 to 8 Cloud Foundry deployments running thousands of applications and hundreds of thous...| OpenTelemetry
The OpenTelemetry Demo has been updated to version 1.6, and introduces alpha support for the OpenTelemetry Log signal! Our thoughts on logs Why are we considering logging support to be in alpha? There are a few reasons. The most important is that this is the first time we’ve shipped the demo with a logging database. We chose OpenSearch as the storage backend for logs because it’s a popular option that aligns with the project’s license. It’s worth noting that the demo doesn’t require...| OpenTelemetry
OTel integration! We’re excited to announce that Tyk API Gateway has first-class support for OpenTelemetry, with native instrumentation built directly into the gateway. With Tyk’s native OpenTelemetry support, developers and API platform teams get end-to-end observability into their API traffic, enabling faster troubleshooting and problem resolution. Why OpenTelemetry API gateways, as the front-line proxies for APIs, play a crucial role in both the management and security of API traffic. ...| OpenTelemetry
Early this year, we launched an effort to stabilize HTTP semantic conventions. Today, we proudly announce that the HTTP semantic conventions are the first OpenTelemetry semantic conventions to be declared stable! This inaugural stable v1.23.0 release marks a substantial advancement from earlier versions, featuring: Enhancements resulting from convergence with the Elastic Common Schema, such as: The url.* namespace, which can be reused in the future by non-HTTP semantic conventions Replacing t...| OpenTelemetry
Synthetic tests are an essential part of the Observability toolkit. They can be used to measure application SLAs, monitor endpoints in various geographies, navigate a web page like a user, or identify post deployment errors before your customers encounter them. This blog is going to focus on HTTP based synthetic availability testing. Many vendors offer various options for availability testing with generous free tiers but monitoring endpoints at enterprise scale can quickly spiral into 1000s o...| OpenTelemetry
The OpenTelemetry project maintainers, members of the governance committee, and technical committee are thrilled to be at KubeCon NA in Chicago from November 6 - 9, 2023. Read on to learn about all the things related OpenTelemetry during KubeCon. OpenTelemetry Contribfest We are happy to announce, that for the first time, you can join the OpenTelemetry maintainers in making OpenTelemetry better for everyone during the OpenTelemetry Contribfest, on Wednesday November 8, 2023 from 2:30pm - 3:55...| OpenTelemetry
Welcome back to OpenTelemetry in Focus for July, 2023! I hope you’re all having a great summer (or if you’re in the southern hemisphere, a great winter!) Let’s get into the updates and releases from the past month. Are you a maintainer with something you’d like featured here? Get in touch with me via email, or on the CNCF Slack #otel-comms channel. Releases and Updates Here are the latest updates from some of our core repositories.| OpenTelemetry
In 2019, we announced that OpenTracing and OpenCensus would be merging to form the OpenTelemetry project. From the start, we considered OpenTelemetry to be the next major version of both OpenTracing and OpenCensus. We are excited to announce that OpenTelemetry has reached feature parity with OpenCensus in C++, .NET, Go, Java, JavaScript, PHP and Python. Stable releases of both the Tracing and Metrics SDKs are available in most of these languages with Go and PHP soon to follow. This means that...| OpenTelemetry
With contributions from Adnan Rahić and Ken Hamric. The OpenTelemetry Demo is a system that simulates a Telescope Shop, consisting of multiple microservices written in different languages, each handling a specific capability of this distributed system. Its purpose is to demonstrate how OpenTelemetry tools and SDKs can be used in an application to obtain telemetry for monitoring results and even to track problems across multiple services. One challenge when maintaining the demo is to add new ...| OpenTelemetry
With contributions from Adriana Villela (Lightstep from ServiceNow). For the OpenTelemetry (OTel) End User Working Group’s fourth End User Q&A session of 2023, we spoke with Jacob Aronoff, Staff Software Engineer at Lightstep from ServiceNow and an OpenTelemetry Operator Maintainer. Read on if you are interested in learning how a vendor is using OTel in-house! This series of interviews is a monthly casual discussion with a team that’s using OpenTelemetry in production. The goal is to shar...| OpenTelemetry
Welcome back to OpenTelemetry in Focus for June, 2023! It’s officially summer, but it’s not just hot outside – we’ve had some major announcements and releases this month. Are you a maintainer with something you’d like featured here? Get in touch with me via email, or on the CNCF Slack #otel-comms channel. Releases and Updates Here are the latest updates from some of our core repositories. Specification Version 1.22 includes a recommendation to reserve the aggregator normative for me...| OpenTelemetry
Previously, in Why Histograms? and Histograms vs Summaries, I went over the basics of histograms and summaries, explaining the tradeoffs, benefits, and limitations of each. Because they’re easy to understand and demonstrate, those posts focused on so-called explicit bucket histograms. The exponential bucket histogram, also referred to as native histogram in Prometheus, is a low-cost, efficient alternative to explicit bucket histograms. In this post, I go through what they are, how they work...| OpenTelemetry
In many ways, histograms and summaries appear quite similar. They both roll up many data points into a data structure for efficient processing, transmission, and storage. They can also both be used to track arbitrary quantiles such as the median or p99 of your data. So how do they differ? Let’s dive in. Histograms Since I just published a post about histograms and when they are useful, I will only provide a quick summary here. A histogram is a data structure which describes the distribution...| OpenTelemetry
With contributions from Rynn Mancuso (Honeycomb) and Reese Lee (New Relic). On Thursday, May 25th, 2023, the OpenTelemetry (OTel) End User Working Group hosted its third End User Q&A session of 2023. We had a bit of a gap due to KubeCon Europe, but now we’re back! This series is a monthly casual discussion with a team using OpenTelemetry in production. The goal is to learn more about their environment, their successes, and the challenges that they face, and to share it with the community, s...| OpenTelemetry
With contributions from Sebastian Choren, Adnan Rahić and Ken Hamric. Kubernetes is an open source system widely used in the cloud native landscape to provide ways to deploy and scale containerized applications in the cloud. Its ability to observe logs and metrics is well-known and documented, but its observability regarding application traces is new. Here is a brief synopsis of the recent activity in the Kubernetes ecosystem: The first discussions started in December 2018 with a first PR on...| OpenTelemetry
Welcome back to OpenTelemetry in Focus for May, 2023! The sun is shining, the sky is blue, and it’s time to run down the latest updates from the OpenTelemetry project! Are you a maintainer with something you’d like featured here? Get in touch with me via email, or on the CNCF Slack #otel-comms channel. Releases and Updates Here are the latest updates from some of our core repositories. Specification Version 1.21 has been released with a variety of important changes, including:| OpenTelemetry
A histogram is a multi-value counter that summarizes the distribution of data points. For example, a histogram may have 3 counters which count the occurrences of negative, positive, and zero values respectively. Given a series of numbers, 3, -9, 7, 6, 0, and -1, the histogram would count 2 negative, 1 zero, and 3 positive values. A single histogram data point is most commonly represented as a bar chart. The above example has only 3 possible output values, but it is common to have many more in...| OpenTelemetry
It’s hard to believe as we prepare our 1.4.0 release but the OpenTelemetry demo is turning 1 year old and it’s been 6 months since we declared general availability with our 1.0.0 release. Project Milestones The demo has achieved remarkable milestones in its first year, with more than 70 contributors, 20 official vendor forks, 780 GitHub stars, and 180K Docker pulls. The project team has been hard at work adding new capabilities and improving on existing ones with more than 460 merged PRs,...| OpenTelemetry
Today, we’re very excited to make a joint announcement with Elastic about the future of Elastic Common Schema (ECS) and the OpenTelemetry Semantic Conventions. The goal is to achieve convergence of ECS and OTel Semantic Conventions into a single open schema that is maintained by OpenTelemetry, so that OpenTelemetry Semantic Conventions truly is a successor of the Elastic Common Schema. OpenTelemetry shares the same interest of improving the convergence of observability and security in this ...| OpenTelemetry
The OpenTelemetry project maintainers, members of the governance committee, and technical committee are excited to be at KubeCon EU in Amsterdam from April 18 - 21, 2023! Read on to learn about all the things related OpenTelemetry during KubeCon. KubeCon Talks and Maintainer Sessions Jaeger: The Future with OpenTelemetry and Metrics by Pavol Loffay, Red Hat & Jonah Kowall, Aiven Wednesday, April 19 • 11:55 - 12:30 Using OpenTelemetry for Application Security, with a Real Life Example by Ron...| OpenTelemetry
Automatic Instrumentation is a process of adding tracing capabilities into user application without modifying its source code. There are several techniques to do that, but all of them more or less work in the same way by injecting additional code into original one during compile time, link time, run-time or by extending the operating system in case of eBPF. This blog post presents method used by OpenTelemetry PHP auto-instrumentation. Prerequisites To use the PHP auto-instrumentation, you’l...| OpenTelemetry
With contributions from Rynn Mancuso (Honeycomb) and Reese Lee (New Relic). On Thursday, March 2nd, 2023, the OpenTelemetry (OTel) End User Working Group hosted its second End User Q&A session of 2023. This series is a monthly casual discussion with a team using OpenTelemetry in production. The goal is to learn more about their environment, their successes, and the challenges that they face, and to share it with the community, so that together, we can help make OpenTelemetry awesome!| OpenTelemetry
Submitting a conference talk in the tech industry can be a thrilling and nerve-wracking experience, especially if it’s your first time. The thought of presenting your ideas to a room full of experts and industry professionals can be intimidating, but also an opportunity to showcase your skills, gain recognition, and network with others in your field. On Wednesday, February 1st, 2023, the OpenTelemetry End User Working Group ran an Observability Abstract Workshop. The goal was to help folks ...| OpenTelemetry
eBay makes a crucial pivot to OpenTelemetry to better align with industry standards for Observability. Introduction Observability provides the eyes and ears to any organization. A major benefit to observability is in preventing the loss of revenue by efficiently surfacing ongoing issues in critical workflows that could potentially impact customer experience. The Observability landscape is an ever-changing one and recent developments in the OpenTelemetry world forced us to rethink our strategy...| OpenTelemetry
Back in May of 2022, the Jaeger project announced native support for the OpenTelemetry Protocol (OTLP). This followed a generous deprecation cycle for the Jaeger client libraries across many languages. With these changes, OpenTelemetry users are now able to send traces into Jaeger with industry-standard OTLP, and the Jaeger client library repositories have been finally archived. We intend to deprecate Jaeger exporters from OpenTelemetry in the near future, and are looking for your feedback to...| OpenTelemetry
Earlier this year, we announced a project to build an OpenTelemetry Demo, representing the breadth of OpenTelemetry features and languages. Today, the Demo SIG is proud to announce OpenTelemetry Demo v1.0! With this demo, you’ll be able to quickly run a complete end-to-end distributed system instrumented with 100% OpenTelemetry Traces and Metrics. One of our primary goals of this project has been to create a robust sample application for developers to use in learning OpenTelemetry, and we...| OpenTelemetry
OpenTelemetry has demonstrated massive growth since its inception in 2019. What started as a handful of OpenTracing and OpenCensus maintainers and collaborators meeting at the Google campus and over Zoom, has now grown into the second-most popular project in the CNCF behind Kubernetes itself. Over 5400 contributors and 700 companies have contributed code, issues, documentation, and invaluable feedback. Our community isn’t just composed of these contributors, however - our end-users, partner...| OpenTelemetry
TL;DR The OpenTelemetry community has taken a good preexisting demo (thanks, Google!) and is in the process of making it even better. Every GA SDK (besides Swift) will be represented, demo support will be extended to Metrics and Logs, and canonical scenarios will be documented for each signal, with fault injection, and more! If you want to skip the details then clone our repository then run docker compose up1 from the command line. There are a couple technology requirements so be sure to chec...| OpenTelemetry
OpenTelemetry’s metrics capabilities are now available as release candidates, starting with Java, .NET, and Python! This means that the specification, APIs, SDKs, and other components that author, capture, process, and otherwise interact with metrics now have the full set of OpenTelemetry metrics functionality and are ready for use. These release candidates will be promoted to general availability throughout the next few weeks. The 1.0 metrics release includes the following: Metrics functio...| OpenTelemetry