fix(deps): update module gopkg.in/datadog/dd-trace-go.v1 to v1.59.0 #163
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![self-hosted-renovatebot[bot]](https://avatars.githubusercontent.com/u/30105612?s=60&v=4){kind=small}
self-hosted-renovatebot
bot
requested review from
cresta-robot and
a team
as code owners
cresta-robot
approved these changes
Jan 9, 2024
self-hosted-renovatebot
bot
deleted the
renovate/gopkg.in-datadog-dd-trace-go.v1-1.x
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.58.1->v1.59.0Release Notes
DataDog/dd-trace-go (gopkg.in/DataDog/dd-trace-go.v1)
v1.59.0Compare Source
Highlights
Important Information
dd-trace-gorequireslibdl.so.2[^2] andlibm.so.6to be present in the deployment environment (except Windows, where Application Security Management is not supported). This should be the case for the vast majority of environments (e.g: Redhat, Debian, Alpine, Amazon Linux, Ubuntu) but might not be the case in some minimal-footprint environments (e.g: BusyBox, docker images fromscratch). In situations when these requirements aren't met, you might see errors similar to (the exact error may be slightly different depending on the platform):ld.sois missing (the environment is unable to load dynamic executables) or is not the expected flavor (the binary was built on one platform, and runs on another which uses a different interpreter):exec /path/to/binary: no such file or directory
libdl.so.2in this example):/path/to/binary: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
If this happens, please create a GitHub issue so we can reconsider this new default requirement. In the meantime, you can work around the problem by adding the
datadog.no_wafbuild tag (go build -tags='datadog.no_waf' ...), which completely disables all Application Security Management features and removes these new requirements.[^2]: In some build environments,
libdlfunctionality is provided bylibc; theldd <binary>command can be used to determine the exact runtime requirementsApplication Security Management (ASM) Remote Activation
Application Security Management (ASM) can now be remotely activated by APM Tracing users via Datadog Remote Configuration, granted that the application was built either:
CGO_ENABLED=0and with theappsecbuild tag (this setup already requiredlibdl.so.2[^2] andlibm.so.6to be present in the deployment environment on previous releases — this remains true).Remote activation can be performed from different places in Datadog UI, such as ASM's Service Setup or APM's Service Catalog (hovering the ASM Status column).
ASM features can still be enabled locally using the
DD_APPSEC_ENABLED=1environment variable.Setting the
datadog.no_wafbuild tag completely disables all ASM features, removing the ability for local as well as remote activation.Application Performance Monitoring (APM)
This release includes a fix to several library integrations which could have previously caused data races related to start options. This was fixed in
database/sql,gin-gonic/gin,go-chi/chi.v5,go-chi/chi,google.golang.org/grpc.v12,google.golang.org/grpc,gorilla/mux,julienschmidt/httprouter,k8s.io/client-go/kubernetes,labstack/echo.v4,labstack/echo,net/http, andurfave/negroni. We recommend you update to this version if you are using any of these integrations.Beta: In-app APM library configuration of trace sampling rate, HTTP header tags and custom tags.
This feature has a known bug: deleting the configuration entry in-app won't reset the configuration locally, this will be fixed in the next version of dd-trace-go (v1.60.0).
What's Changed
Application Security Management (ASM)
Application Performance Monitoring (APM)
General
New Contributors
Full Changelog: DataDog/dd-trace-go@v1.58.0...v.1.59.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.