Skip to content
Switch branches/tags

Latest commit

* Fix IPv6 handling errors in semconv.NetAttributesFromHTTPRequest

fixes #2283

* Enter PR number in CHANGELOG

* Remove unnecessary creation and then assignment

Standardize order of checks for IP, Name, Port

* Assume happy path when parsing host and port

i.e. assume net.SplitHostPort(input) will succeed

* Get rid of uint64 for port

* Fix git merge of main by adding back strings import

Co-authored-by: Tyler Yahn <>
Co-authored-by: Tyler Yahn <>

Git stats


Failed to load latest commit information.
Latest commit message
Commit time
May 16, 2019


CI PkgGoDev Go Report Card Slack

OpenTelemetry-Go is the Go implementation of OpenTelemetry. It provides a set of APIs to directly measure performance and behavior of your software and send this data to observability platforms.

Project Status

Signal Status Project
Traces Stable N/A
Metrics Alpha N/A
Logs Frozen [1] N/A
  • [1]: The Logs signal development is halted for this project while we develop both Traces and Metrics. No Logs Pull Requests are currently being accepted.

Progress and status specific to this repository is tracked in our local project boards and milestones.

Project versioning information and stability guarantees can be found in the versioning documentation.


This project is tested on the following systems.

OS Go Version Architecture
Ubuntu 1.17 amd64
Ubuntu 1.16 amd64
Ubuntu 1.15 amd64
Ubuntu 1.17 386
Ubuntu 1.16 386
Ubuntu 1.15 386
MacOS 1.17 amd64
MacOS 1.16 amd64
MacOS 1.15 amd64
Windows 1.17 amd64
Windows 1.16 amd64
Windows 1.15 amd64
Windows 1.17 386
Windows 1.16 386
Windows 1.15 386

While this project should work for other systems, no compatibility guarantees are made for those systems currently.

Getting Started

You can find a getting started guide on

OpenTelemetry's goal is to provide a single set of APIs to capture distributed traces and metrics from your application and send them to an observability platform. This project allows you to do just that for applications written in Go. There are two steps to this process: instrument your application, and configure an exporter.


To start capturing distributed traces and metric events from your application it first needs to be instrumented. The easiest way to do this is by using an instrumentation library for your code. Be sure to check out the officially supported instrumentation libraries.

If you need to extend the telemetry an instrumentation library provides or want to build your own instrumentation for your application directly you will need to use the package. The included examples are a good way to see some practical uses of this process.


Now that your application is instrumented to collect telemetry, it needs an export pipeline to send that telemetry to an observability platform.

All officially supported exporters for the OpenTelemetry project are contained in the exporters directory.

Exporter Metrics Traces

Additionally, OpenTelemetry community supported exporters can be found in the contrib repository.


See the contributing documentation.