- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
The Go Tracer requires Go 1.18+
and Datadog Agent >= 5.21.1
. For a full list of Datadog’s Go version and framework support (including legacy and maintenance versions), see the Compatibility Requirements page.
Before you begin, make sure you’ve already installed and configured the Agent.
There are two ways to instrument your Go application:
Refer to the instructions in the section corresponding to your preference below:
Manual instrumentation
Datadog has a series of pluggable packages which provide out-of-the-box support for instrumenting a series of libraries and frameworks. A list of these packages can be found in the Compatibility Requirements page. Import these packages into your application and follow the configuration instructions listed alongside each Integration.
If needed, configure the tracing library to send application performance telemetry data as you require, including setting up Unified Service Tagging. Read Library Configuration for details.
For configuration instructions and details about using the API, see the Datadog API documentation.
Compile-time instrumentation (private beta)
Orchestrion is under active development, and Datadog is eager to hear from you. Request access if you are interested and would like to share your experience.
Request AccessOrchestrion automatically adds instrumentation to Go applications during compilation, eliminating the need for code changes. It provides comprehensive tracing coverage and enables exclusive security features:
Orchestrion is under active development and supports a subset of integrations available in the tracing library. For the latest list of supported frameworks and their minimum Orchestrion versions, see the Supported frameworks.
To install and set up Orchestrion:
Install Orchestrion:
go install github.com/DataDog/orchestrion@latest
$(go env GOBIN)
(or $(go env GOPATH)/bin
) is in your $PATH
.Register Orchestrion in your project’s go.mod
:
orchestrion pin
Commit changes to your version control system:
git commit -m "chore: enable orchestrion" go.mod go.sum orchestrion.tool.go
Now you can manage your dependency on orchestrion
like any other dependency using the go.mod
file.
Use one of these methods to enable Orchestrion in your build process:
orchestrion
to your usual go
commands:orchestrion go build .
orchestrion go run .
orchestrion go test ./...
-toolexec="orchestrion toolexec"
argument to your go
commands:go build -toolexec="orchestrion toolexec" .
go run -toolexec="orchestrion toolexec" .
go test -toolexec="orchestrion toolexec" ./...
$GOFLAGS
environment variable to inject Orchestrion, and use go
commands normally:# Make sure to include the quotes as shown below, as these are required for
# the Go toolchain to parse GOFLAGS properly!
export GOFLAGS="${GOFLAGS} '-toolexec=orchestrion toolexec'"
go build .
go run .
go test ./...
To create custom trace spans for functions accepting context.Context
or *http.Request
arguments, add the //dd:span
directive comment to the function declaration:
example.go
//dd:span custom_tag:tag_value
func CriticalPathFunction(ctx context.Context) {
// ... implementation details ...
}
This also works with function literal expressions:
example.go
//dd:span custom_tag:tag_value
handler := func(w http.ResponseWriter, r *http.Request) {
// ... implementation details ...
}
You can use the tracing library in your Orchestrion-built application. This is useful for instrumenting frameworks not yet supported by Orchestrion. However, be aware that this may result in duplicated trace spans in the future as Orchestrion support expands. Review the release notes when updating your orchestrion
dependency to stay informed about new features and adjust your manual instrumentation as necessary.
Your Orchestrion-built application includes continuous profiler instrumentation.
To enable the profiler, set the environment variable DD_PROFILING_ENABLED=true
at run time.
Library | Minimum orchestrion version |
---|---|
database/sql | v0.7.0 |
github.com/gin-gonic/gin | v0.7.0 |
github.com/go-chi/chi/v5 | v0.7.0 |
github.com/go-chi/chi | v0.7.0 |
github.com/go-redis/redis/v7 | v0.7.0 |
github.com/go-redis/redis/v8 | v0.7.0 |
github.com/gofiber/fiber/v2 | v0.7.0 |
github.com/gomodule/redigo/redis | v0.7.0 |
github.com/gorilla/mux | v0.7.0 |
github.com/jinzhu/gorm | v0.7.0 |
github.com/labstack/echo/v4 | v0.7.0 |
google.golang.org/grpc | v0.7.0 |
gorm.io/gorm | v0.7.0 |
net/http | v0.7.0 |
go.mongodb.org/mongo-driver/mongo | v0.7.3 |
k8s.io/client-go | v0.7.4 |
github.com/hashicorp/vault | v0.7.4 |