Supported libraries
You are viewing the English version of this page because it has not yet been fully translated. Interested in helping out? See Contributing.
The tool ships instrumentation packages for the following libraries and frameworks. When your application or its dependencies use one of them, the matching instrumentation is injected automatically at build time.
| Library or framework | Import path | Instrumented operations |
|---|---|---|
| HTTP (standard library) | net/http | Client and server requests |
| gRPC | google.golang.org/grpc | Client and server calls |
| SQL databases | database/sql | Database calls |
| Gin | github.com/gin-gonic/gin | Server requests |
| Redis | github.com/redis/go-redis/v9 | Client commands |
| MongoDB | go.mongodb.org/mongo-driver/mongo | Client commands |
| Kafka | github.com/segmentio/kafka-go | Produced and consumed messages |
| OpenAI | github.com/openai/openai-go (v1 – v3) | Client calls |
| Kubernetes client | k8s.io/client-go/tools/cache | Informer cache operations |
| slog (standard library) | log/slog | Log records |
| Logrus | github.com/sirupsen/logrus | Log records |
HTTP and gRPC instrumentation produce spans and metrics, including automatic
context propagation between services.
Instrumentation follows the OpenTelemetry
semantic conventions for each library. Go runtime
metrics are collected by default and can be turned off by adding
runtimemetrics to OTEL_GO_DISABLED_INSTRUMENTATIONS.
The set of supported library versions is declared by each instrumentation’s rules. For the authoritative, up-to-date list, see the instrumentation packages in the repository.
Requesting a library
If a library you rely on isn’t instrumented yet, open a feature request. You can also add instrumentation yourself: the repository’s instrumentation guide walks through defining rules and implementing hooks for a new library.
Comentariu
A fost utilă această pagină?
Thank you. Your feedback is appreciated!
Please let us know how we can improve this page. Your feedback is appreciated!