Added integration support for DataDog APM Tracing
This commit is contained in:
parent
ba8c9295ac
commit
3192307d59
61 changed files with 9999 additions and 5 deletions
22
vendor/gopkg.in/DataDog/dd-trace-go.v1/ddtrace/ext/priority.go
generated
vendored
Normal file
22
vendor/gopkg.in/DataDog/dd-trace-go.v1/ddtrace/ext/priority.go
generated
vendored
Normal file
|
@ -0,0 +1,22 @@
|
|||
package ext
|
||||
|
||||
// Priority is a hint given to the backend so that it knows which traces to reject or kept.
|
||||
// In a distributed context, it should be set before any context propagation (fork, RPC calls) to be effective.
|
||||
|
||||
const (
|
||||
// PriorityUserReject informs the backend that a trace should be rejected and not stored.
|
||||
// This should be used by user code overriding default priority.
|
||||
PriorityUserReject = -1
|
||||
|
||||
// PriorityAutoReject informs the backend that a trace should be rejected and not stored.
|
||||
// This is used by the builtin sampler.
|
||||
PriorityAutoReject = 0
|
||||
|
||||
// PriorityAutoKeep informs the backend that a trace should be kept and not stored.
|
||||
// This is used by the builtin sampler.
|
||||
PriorityAutoKeep = 1
|
||||
|
||||
// PriorityUserKeep informs the backend that a trace should be kept and not stored.
|
||||
// This should be used by user code overriding default priority.
|
||||
PriorityUserKeep = 2
|
||||
)
|
Loading…
Add table
Add a link
Reference in a new issue