• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

.circleci/H22-Apr-2021-210177

contrib/H22-Apr-2021-33,32126,588

ddtrace/H22-Apr-2021-46,23533,382

internal/H22-Apr-2021-621451

profiler/H22-Apr-2021-2,5261,994

.gitignoreH A D22-Apr-2021506 2722

.gitlab-ciH A D22-Apr-2021940 2622

CONTRIBUTING.mdH A D22-Apr-20212 KiB4830

LICENSEH A D22-Apr-202112.7 KiB235196

LICENSE-3rdparty.csvH A D22-Apr-2021111 22

LICENSE-APACHEH A D22-Apr-202111.1 KiB201169

LICENSE-BSD3H A D22-Apr-20211.5 KiB2522

MIGRATING.mdH A D22-Apr-20215.9 KiB10567

NOTICEH A D22-Apr-2021146 53

README.mdH A D22-Apr-20212.1 KiB3623

checkcopyright.goH A D22-Apr-20211.3 KiB5642

checkmilestone.goH A D22-Apr-20211.1 KiB5645

codecov.ymlH A D22-Apr-2021423 3127

go.modH A D22-Apr-2021244 118

go.sumH A D22-Apr-202195.1 KiB1,0011,000

README.md

1[![CircleCI](https://circleci.com/gh/DataDog/dd-trace-go/tree/v1.svg?style=svg)](https://circleci.com/gh/DataDog/dd-trace-go/tree/v1)
2[![Godoc](http://img.shields.io/badge/godoc-reference-blue.svg?style=flat)](https://godoc.org/gopkg.in/DataDog/dd-trace-go.v1/ddtrace)
3[![codecov](https://codecov.io/gh/DataDog/dd-trace-go/branch/v1/graph/badge.svg?token=jGG20Xhv8i)](https://codecov.io/gh/DataDog/dd-trace-go)
4
5### Installing
6
7```bash
8go get gopkg.in/DataDog/dd-trace-go.v1/...
9```
10
11Requires:
12
13* Go >= 1.12
14* Datadog's Trace Agent >= 5.21.1
15
16### Documentation
17
18The API is documented on [godoc](https://godoc.org/gopkg.in/DataDog/dd-trace-go.v1/ddtrace) as well as Datadog's [official documentation](https://docs.datadoghq.com/tracing/setup/go/). If you are migrating
19from an older version of the tracer (e.g. 0.6.x) you may also find the [migration document](https://github.com/DataDog/dd-trace-go/blob/v1/MIGRATING.md) we've put together helpful.
20
21### Contributing
22
23Before considering contributions to the project, please take a moment to read our brief [contribution guidelines](https://github.com/DataDog/dd-trace-go/blob/v1/CONTRIBUTING.md).
24
25### Testing
26
27Tests can be run locally using the Go toolset. The grpc.v12 integration will fail (and this is normal), because it covers for deprecated methods. In the CI environment
28we vendor this version of the library inside the integration. Under normal circumstances this is not something that we want to do, because users using this integration
29might be running versions different from the vendored one, creating hard to debug conflicts.
30
31To run integration tests locally, you should set the `INTEGRATION` environment variable. The dependencies of the integration tests are best run via Docker. To get an
32idea about the versions and the set-up take a look at our [CI config](https://github.com/DataDog/dd-trace-go/blob/v1/.circleci/config.yml).
33
34The best way to run the entire test suite is using the [CircleCI CLI](https://circleci.com/docs/2.0/local-jobs/). Simply run `circleci build`
35in the repository root. Note that you might have to increase the resources dedicated to Docker to around 4GB.
36