Feature Activation
Custom Go Tracer start-up
All applications built using orchestrion automatically start the Datadog
tracer at the beginning of the main function using the tracer library’s
default configuration. The recommended way to configure the tracer is by using
the designated environment variables, such as DD_ENV, DD_SERVICE,
DD_VERSION, etc… You can get more information on what environment variables
are available in the documentation.
If the main function is annotated with the //dd:ignore directive, the tracer
will not be started automatically, and you are responsible for calling
tracer.Start
with your preferred configuration options.
Enabling the Go Profiler
All applications built using orchestrion automatically start the Datadog
continuous profiler if the DD_PROFILING_ENABLED environment variable is set
to 1 or true. If profiling is enabled via the
Datadog Admission Controller, DD_PROFILING_ENABLED can be
set to auto.
When enabled, the continuous profiler will activate the following profiles:
Enabling Application Security features
Datadog Application Security (ASM) features are built into the tracer library, but need to be enabled at run-time. The Enabling ASM for Go documentation explains how to enable Application Security for instrumented go applications.
In the majority of cases, all that’s needed is to set DD_APPSEC_ENABLED to 1
or true.
Datadog’s Application Security features are only supported on Linux (AMD64, ARM64) and macOS (AMD64, ARM64).
On Linux platforms, the Datadog in-app WAF needs the libc.so.6 and
libpthread.so.0 shared libraries to be available; even if CGO_ENABLED=1.
If your are building your applications in environments where CGO_ENABLED=0,
Application Security features are only available if you specify the appsec
build tag (orchestrion go build -tags=appsec .).
For more information, refer to the Enabling ASM for Go documentation.
Building applications with orchestrion allows you to maximize coverage for
RASP features, such as
automatic protection against SQL Injection attacks.