-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Version of orchestrion
v1.4.0
Describe what happened:
Tested out a deployment with v1.4.0 built go application with the following orchestrion.tools.go
//go:build tools
package tools
import (
_ "github.com/DataDog/dd-trace-go/contrib/confluentinc/confluent-kafka-go/kafka.v2/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/database/sql/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/go-chi/chi.v5/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/google.golang.org/api/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/google.golang.org/grpc/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/gorm.io/gorm.v1/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/jackc/pgx.v5/v2" // integration
_ "github.com/DataDog/dd-trace-go/contrib/net/http/v2" // integration
_ "github.com/DataDog/orchestrion" // integration
)
Note: I use pgx with gorm as my Postgres driver (I don't use any other DBMS)
Describe what you expected:
I expected DataDog tracer startup to show all features and respect DBM_PROPAGATION_MODE=full as an environment variable
2025/06/10 19:01:22 Datadog Tracer v2.0.0 WARN: Using DBM_PROPAGATION_MODE in 'full' mode is not supported for SQL Server, downgrading to 'service' mode. See https://docs.datadoghq.com/database_monitoring/connect_dbm_and_apm/ for more info.
This shows up in the k8s pod logs, and no startup logs end up showing.
Steps to reproduce the issue:
I'll have to figure out a smaller reproducible build of code to demonstrate the problem, but hopefully I'll be able to point to a repository soon once I can verify that indeed it's a problem with how orchestrion has orchestrated the build.
Additional environment details (Version of Go, Operating System, etc.):
Go 1.24
OS: linux/amd64
Using go tools installed orchestrion.