README.md
1[](https://godoc.org/gopkg.in/DataDog/dd-trace-go.v1/contrib)
2
3The purpose of these packages is to provide tracing on top of commonly used packages from the standard library as well as the
4community in a "plug-and-play" manner. This means that by simply importing the appropriate path, functions are exposed having
5 the same signature as the original package. These functions return structures which embed the original return value, allowing
6them to be used as they normally would with tracing activated out of the box.
7
8All of these libraries are supported by our [APM product](https://www.datadoghq.com/apm/).
9
10:warning: These libraries are not built to be used with Opentracing. Opentracing integrations can be found in [their own organisation](https://github.com/opentracing-contrib/).
11
12### Usage
13
14First, find the library which you'd like to integrate with. The naming convention for the integration packages is:
15
16* If the package is from the standard library (eg. `database/sql`), it will be located at the same path.
17* If the package is hosted on Github (eg. `github.com/user/repo`) and has version `v2.1.0`, it will be located at the shorthand path `user/repo.v2`.
18* If the package is from anywhere else (eg. `google.golang.org/grpc`) and has no stable version, it can be found under the full import path, followed by the version suffix (in this example `.v0`).
19* All new integrations should be suffixed with `.vN` where `N` is the major version that is being covered.
20* The package itself should retain its un-versioned name. For example, the integration under `user/repo.v2` stays as `package repo`, and does not become `package repo.v2`
21
22Each integration comes with thorough documentation and usage examples. A good overview can be seen on our
23[godoc](https://godoc.org/gopkg.in/DataDog/dd-trace-go.v1/contrib) page.
24
){kind=link}