eb988d7a85
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [go.opentelemetry.io/collector/pdata](https://redirect.github.com/open-telemetry/opentelemetry-collector) | `v1.24.0` -> `v1.25.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)</summary> ### [`v1.25.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1250v01190) ##### 🛑 Breaking changes 🛑 - `exporterhelper`: Rename exporter span signal specific attributes (e.g. "sent_spans" / "send_failed_span") to "items.sent" / "items.failed". ([#​12165](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12165)) - `cmd/mdatagen`: Remove dead field `telemetry::level` ([#​12144](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12144)) - `exporterhelper`: Change exporter ID to be a Span level attribute instead on each event. ([#​12164](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12164)) This does not have an impact on the level of information emitted, but on the structure of the Span. - `cmd/mdatagen`: Remove `level` field from metrics definition ([#​12145](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12145)) This mechanism will be added back once a new views mechanism is implemented. ##### 💡 Enhancements 💡 - `configtls`: Allow users to mention their preferred curve types for ECDHE handshake ([#​12174](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12174)) - `service`: remove custom code and instead use config package to instantiate meter provider. ([#​11611](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11611)) - `otelcol`: Adds support for listing config providers in components command's output ([#​11570](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11570)) - `general`: Reduce memory allocations when loading configuration and parsing component names ([#​11964](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11964)) ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Fix bug that the exporter with new batcher may have been marked as non mutation. ([#​12239](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12239)) Only affects users that manually turned on `exporter.UsePullingBasedExporterQueueBatcher` featuregate. - `service`: Preserve URL normalization logic that was present before. ([#​12254](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12254)) - `confighttp`: confighttp.ToServer now sets ErrorLog with a default logger backed by Zap ([#​11820](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11820)) This change ensures that the http.Server's ErrorLog is correctly set using Zap's logger at the error level, addressing the issue of error logs being printed using a different logger. - `exporterhelper`: Fix context propagation for DisabledBatcher ([#​12231](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12231)) - `mdatagen`: apply fieldalignment to generated code ([#​12125](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12125)) - `mdatagen`: Fix bug where Histograms were marked as not supporting temporaly aggregation ([#​12168](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12168)) - `exporterhelper`: Fix MergeSplit issue that ignores the initial message size. ([#​12257](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12257)) - `service`: Include validation errors from telemetry.Config when validating the service config ([#​12100](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12100)) Previously validation errors were only printed to the console - `service-telemetry`: pass the missing async error channel into service telemetry settings ([#​11417](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11417)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-go). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNDUuMCIsInVwZGF0ZWRJblZlciI6IjM5LjE0NS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
OpenTelemetry-Go
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 |
|---|---|
| Traces | Stable |
| Metrics | Stable |
| Logs | Beta1 |
Progress and status specific to this repository is tracked in our project boards and milestones.
Project versioning information and stability guarantees can be found in the versioning documentation.
Compatibility
OpenTelemetry-Go ensures compatibility with the current supported versions of the Go language:
Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.
For versions of Go that are no longer supported upstream, opentelemetry-go will stop ensuring compatibility with these versions in the following manner:
- A minor release of opentelemetry-go will be made to add support for the new supported release of Go.
- The following minor release of opentelemetry-go will remove compatibility testing for the oldest (now archived upstream) version of Go. This, and future, releases of opentelemetry-go may include features only supported by the currently supported versions of Go.
Currently, this project supports the following environments.
| OS | Go Version | Architecture |
|---|---|---|
| Ubuntu | 1.23 | amd64 |
| Ubuntu | 1.22 | amd64 |
| Ubuntu | 1.23 | 386 |
| Ubuntu | 1.22 | 386 |
| Linux | 1.23 | arm64 |
| Linux | 1.22 | arm64 |
| macOS 13 | 1.23 | amd64 |
| macOS 13 | 1.22 | amd64 |
| macOS | 1.23 | arm64 |
| macOS | 1.22 | arm64 |
| Windows | 1.23 | amd64 |
| Windows | 1.22 | amd64 |
| Windows | 1.23 | 386 |
| Windows | 1.22 | 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.io.
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.
Instrumentation
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 Go otel package. The examples are a good way to see some practical uses of this process.
Export
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 | Logs | Metrics | Traces |
|---|---|---|---|
| OTLP | ✓ | ✓ | ✓ |
| Prometheus | ✓ | ||
| stdout | ✓ | ✓ | ✓ |
| Zipkin | ✓ |
Contributing
See the contributing documentation.