cerc-io/ipld-eth-server
18
0
Fork 1
Code Issues 10 Pull Requests 1 Actions Packages Projects Releases 37 Wiki Activity
ff110592bd
ipld-eth-server/vendor/gopkg.in/DataDog/dd-trace-go.v1/contrib
History
Rob Mulholand ff110592bd Add Vat init transformer
2018-09-11 16:30:29 -05:00
..
aws/aws-sdk-go/aws Add Vat init transformer 2018-09-11 16:30:29 -05:00
bradfitz/gomemcache/memcache Add Vat init transformer 2018-09-11 16:30:29 -05:00
database/sql Add Vat init transformer 2018-09-11 16:30:29 -05:00
garyburd/redigo Add Vat init transformer 2018-09-11 16:30:29 -05:00
gin-gonic/gin Add Vat init transformer 2018-09-11 16:30:29 -05:00
globalsign/mgo Add Vat init transformer 2018-09-11 16:30:29 -05:00
go-redis/redis Add Vat init transformer 2018-09-11 16:30:29 -05:00
gocql/gocql Add Vat init transformer 2018-09-11 16:30:29 -05:00
google.golang.org Add Vat init transformer 2018-09-11 16:30:29 -05:00
gorilla/mux Add Vat init transformer 2018-09-11 16:30:29 -05:00
graph-gophers/graphql-go Add Vat init transformer 2018-09-11 16:30:29 -05:00
internal Add Vat init transformer 2018-09-11 16:30:29 -05:00
jmoiron/sqlx Add Vat init transformer 2018-09-11 16:30:29 -05:00
julienschmidt/httprouter Add Vat init transformer 2018-09-11 16:30:29 -05:00
k8s.io/client-go/kubernetes Add Vat init transformer 2018-09-11 16:30:29 -05:00
net/http Add Vat init transformer 2018-09-11 16:30:29 -05:00
olivere/elastic Add Vat init transformer 2018-09-11 16:30:29 -05:00
README.md Add Vat init transformer 2018-09-11 16:30:29 -05:00

README.md

Godoc

The purpose of these packages is to provide tracing on top of commonly used packages from the standard library as well as the community in a "plug-and-play" manner. This means that by simply importing the appropriate path, functions are exposed having the same signature as the original package. These functions return structures which embed the original return value, allowing them to be used as they normally would with tracing activated out of the box.

All of these libraries are supported by our APM product.

Usage

First, find the library which you'd like to integrate with. The naming convention for the integration packages is:

  • If the package is from the standard library (eg. database/sql), it will be located at the same path.
  • If the package is hosted on Github (eg. github.com/user/repo), it will be located at the shorthand path user/repo.
  • If the package is from anywhere else (eg. google.golang.org/grpc), it can be found under the full import path.

Each integration comes with thorough documentation and usage examples. A good overview can be seen on our godoc page.