chore(deps): bump gopkg.in/DataDog/dd-trace-go.v1 from 1.19.0 to 1.25.0

[dependabot-preview]

Bumps gopkg.in/DataDog/dd-trace-go.v1 from 1.19.0 to 1.25.0.

Release notes

Sourced from gopkg.in/DataDog/dd-trace-go.v1's releases.

1.25.0

This release incorporates support for Go modules, additional options for the profiler, improved support for log injection, and various improvements and fixes for the contrib packages.

Upgrade Notes

• Users of our contrib/shopify/sarama integration will need to change the import path from gopkg.in/Shopify/sarama.v1 to github.com/Shopify/sarama if they have not already done so. This is the result of github.com/Shopify/sarama using the github path as their canonical name in their go.mod file. Please see (Shopify/sarama#1510) and (DataDog/dd-trace-go#672) for more details.

Features

• profiler: add WithSite option and DD_SITE environment variable. (#644)
• ddtrace/tracer: improve support for log injection (#657, #676)
• contrib/internal/httputil: add HTTP host tag (#648)
• contrib/google.golang.org/grpc: add metadata and request parameter tags for grpc calls (#647) (Thanks, @mingrammer)
• contrib/jinzhu/gorm: add context getter for gorm.db (#667) (Thanks, @zhammer)
• all: migrate to modules (#672)
• ddtrace/tracer: send all global tags with metrics (#673) (Thanks, @DarrenTsung)
• profiler: support agent-based deployments and have those as default. (#668)

Fixes

• contrib/google.golang.org/grpc: fix a data race in config (#670) (Thanks, @ktr0731)

To view all changes check out new commits and the 1.25.0 milestone.

1.24.1

This release removes the WithValueTags option from the contrib/bradfitz/gomemcache integration.

WithValueTags could be problematic for multiple reasons such as producing unexpectedly large quantities of data, and possible security issues. We do not want to provide APIs with unexpected or potentially dangerous behavior.

1.24.0

This release includes quite a few bug fixes and some small features, like profiler support for the DD_ENV, DD_VERSION, DD_SERVICE, and DD_TAGS environment variables.

Features

• contrib/gocql/gocql: update with latest changes to WithContext (#624) (Thanks @ericjster)
• profiler: add support for DD_ENV, DD_VERSION, DD_SERVICE, and DD_TAGS. (#632)
• ddtrace/tracer: add WithHTTPClient and increase default HTTP timeout (#636)
• contrib/bradfitz/gomemcache: trace item info for memcached operations (#642) (Thanks @mingrammer)

Fixes

• contrib/internal/httputil: only set status once with WriteHeader (#629)
• contrib/gocql/gocql: do not assume slice length (#641)
• profiler: use correct URL for profiler backend (#645)
• internal/globalconfig: fix wrong mutex acquired for SetServiceName (#659) (Thanks @vikpattabi)

To view all changes check out new commits and the 1.24.0 milestone.

1.23.3

This release contains a patch which acquires the correct mutex when setting the global service name. (#659) (Thanks @vikpattabi)

1.23.2

This release contains a patch which corrects the profiler backend URL (#645).

Commits

• afab3a8 profiler: support agent-based deployments and have those as default. (#668)
• 5dd3603 README: update go get path to include profiler
• e713241 ddtrace/tracer: send all global tags instead of just env (#673)
• 8da2db7 circleci: improve speed (#680)
• 307997d ddtrace/tracer: add quotes to trace and span id in format (#676)
• 9dc9e22 Revert "contrib/bradfitz/gomemcache: trace item info for memcached operations...
• 7b2e805 contrib/google.golang.org/grpc: fix a data race in config (#670)
• ee88309 all: migrate to modules (#672)
• 4ceb1aa contrib/jinzhu/gorm: add context getter for gorm.db (#667)
• f511c53 internal/version: update version to v1.25.0 (#665)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[jenkins-x-bot]

Hi @dependabot-preview[bot]. Thanks for your PR.

I'm waiting for a cloudbees or jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[jenkins-x-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ccojocar
You can assign the PR to them by writing /assign @ccojocar in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment