| 1 |
Source: golang-github-containerd-otelttrpc |
| 2 |
Section: golang |
| 3 |
Priority: optional |
| 4 |
Maintainer: Debian Go Packaging Team <[email protected]> |
| 5 |
Uploaders: Reinhard Tartler <[email protected]>, |
| 6 |
Rules-Requires-Root: no |
| 7 |
Build-Depends: debhelper-compat (= 13), |
| 8 |
dh-sequence-golang, |
| 9 |
golang-any, |
| 10 |
golang-github-containerd-ttrpc-dev, |
| 11 |
golang-github-stretchr-testify-dev, |
| 12 |
golang-google-grpc-dev, |
| 13 |
golang-google-protobuf-dev, |
| 14 |
golang-opentelemetry-otel-dev, |
| 15 |
Testsuite: autopkgtest-pkg-go |
| 16 |
Standards-Version: 4.7.2 |
| 17 |
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-containerd-otelttrpc |
| 18 |
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-containerd-otelttrpc.git |
| 19 |
Homepage: https://github.com/containerd/otelttrpc |
| 20 |
XS-Go-Import-Path: github.com/containerd/otelttrpc |
| 21 |
|
| 22 |
Package: golang-github-containerd-otelttrpc-dev |
| 23 |
Architecture: all |
| 24 |
Multi-Arch: foreign |
| 25 |
Depends: golang-github-containerd-ttrpc-dev, |
| 26 |
golang-github-stretchr-testify-dev, |
| 27 |
golang-google-grpc-dev, |
| 28 |
golang-google-protobuf-dev, |
| 29 |
golang-opentelemetry-otel-dev, |
| 30 |
${misc:Depends}, |
| 31 |
Description: OpenTelemetry instrumentation for ttrpc (Go) |
| 32 |
This package provides OpenTelemetry instrumentation middleware for |
| 33 |
ttRPC-based systems. It implements both client-side and server-side tracing |
| 34 |
interceptors that integrate with the containerd project's ttRPC |
| 35 |
implementation (github.com/containerd/ttrpc). The middleware enables |
| 36 |
automatic propagation of distributed tracing context and collection of |
| 37 |
granular performance metrics for ttRPC calls. |
| 38 |
. |
| 39 |
Designed specifically for low-overhead instrumentation in container runtimes, |
| 40 |
it allows operators to trace request flows across containerd components and |
| 41 |
associated container management systems. The generated traces can be exported |
| 42 |
to any OpenTelemetry-compatible backend for observability and analysis. |