A fork of Gitea (see branch `mj`) adding Majority Judgment Polls 𐄷 over Issues and Merge Requests. https://git.mieuxvoter.fr
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
domi41 f70b353236 fix: issue with the biggest group calculus 1 year ago
..
codes go1.16 (#14783) 1 year ago
internal [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
label [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
metric go1.16 (#14783) 1 year ago
propagation [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
trace go1.16 (#14783) 1 year ago
unit fix: issue with the biggest group calculus 1 year ago
.gitignore go1.16 (#14783) 1 year ago
.gitmodules [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
.golangci.yml [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
CHANGELOG.md go1.16 (#14783) 1 year ago
CODEOWNERS go1.16 (#14783) 1 year ago
CONTRIBUTING.md go1.16 (#14783) 1 year ago
LICENSE [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
Makefile go1.16 (#14783) 1 year ago
Makefile.protos go1.16 (#14783) 1 year ago
README.md go1.16 (#14783) 1 year ago
RELEASING.md go1.16 (#14783) 1 year ago
VERSIONING.md [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
doc.go [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
error_handler.go [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
get_main_pkgs.sh [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
go.mod go1.16 (#14783) 1 year ago
go.sum go1.16 (#14783) 1 year ago
handler.go [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
pre_release.sh go1.16 (#14783) 1 year ago
propagation.go [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
tag.sh [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
trace.go go1.16 (#14783) 1 year ago
verify_examples.sh [Vendor] Update go-redis to v8.5.0 (#13749) 1 year ago
version.go go1.16 (#14783) 1 year ago

README.md

OpenTelemetry-Go

CI PkgGoDev Go Report Card Gitter

The Go OpenTelemetry implementation.

Project Status

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.

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.

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.opentelemetry.io/otel/api package. The included 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.

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.

Contributing

See the contributing documentation.