In #16055 it appears that the simple 5s deadline doesn't work for large file writes. Now we can't - or at least shouldn't just set no deadline as go will happily let these connections block indefinitely. However, what seems reasonable is to set some minimum rate we expect for writing. This PR suggests the following algorithm: * Every write has a minimum timeout of 5s (adjustable at compile time.) * If there has been a previous write - then consider its previous deadline, add half of the minimum timeout + 2s per kb about to written. * If that new deadline is after the minimum timeout use that. Fix #16055 Signed-off-by: Andrew Thornton <email@example.com> Co-authored-by: 6543 <firstname.lastname@example.org>
|1 year ago|
|codes||2 years ago|
|internal||2 years ago|
|label||2 years ago|
|metric||2 years ago|
|propagation||2 years ago|
|trace||2 years ago|
|unit||2 years ago|
|.gitignore||2 years ago|
|.gitmodules||2 years ago|
|.golangci.yml||2 years ago|
|CHANGELOG.md||2 years ago|
|CODEOWNERS||2 years ago|
|CONTRIBUTING.md||2 years ago|
|LICENSE||2 years ago|
|Makefile||2 years ago|
|Makefile.protos||2 years ago|
|README.md||2 years ago|
|RELEASING.md||2 years ago|
|VERSIONING.md||2 years ago|
|doc.go||2 years ago|
|error_handler.go||2 years ago|
|get_main_pkgs.sh||2 years ago|
|go.mod||2 years ago|
|go.sum||2 years ago|
|handler.go||2 years ago|
|pre_release.sh||2 years ago|
|propagation.go||2 years ago|
|tag.sh||2 years ago|
|trace.go||2 years ago|
|verify_examples.sh||2 years ago|
|version.go||2 years ago|
The Go OpenTelemetry implementation.
Warning: this project is currently in a pre-GA phase. Backwards incompatible changes may be introduced in subsequent minor version releases as we work to track the evolving OpenTelemetry specification and user feedback.
Our progress towards a GA release candidate is tracked in this project board. This release candidate will follow semantic versioning and will be released with a major version greater than zero.
Project versioning information and stability guarantees can be found in the versioning documentation.
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.
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.opentelemetry.io/otel/api 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.
You can find officially supported exporters here and in the companion contrib repository. Additionally, there are many vendor specific or 3rd party exporters for OpenTelemetry. These exporters are broken down by trace and metric support.
See the contributing documentation.