v1.43.0

Summary

This version notably brings:

• Application Security Monitoring on linux/arm64 and darwin/arm64
• The profiler now captures its own CPU overhead. Previously, CPU profiling could be stopped before follow-on work processing the other profile types completed. There is now proper synchronization so this work is captured. Note that there may be a small (<1%) increase in CPU time on profiles. This is not new overhead, or a regression. It is just work that was already being done, now more accurately reflected.
• The new ddtrace.UseLogger function can be used to configure logging for both the tracer and profiler.

A couple of improvements and fixes can also be found in the list of changes below.

Changes

General

• internal/telemetry: support DD_TELEMETRY_HEARTBEAT_INTERVAL configuration environment variable by @katiehockman in #1475

Application Performance Monitoring (APM)

• contrib/99designs/gqlgen: fix go module resolution issue by @david-alza in #1457
• contrib/net/http: don't set the request path in the Route field by @bitterbit in #1471
• contrib/net/http: ensure NewServeMux respects WithResourceNamer option by @mccutchen in #1436
• contrib/database/sql: fix race condition when registering drivers by @rafaeljusto in #1450
• ddtrace: make UseLogger public by @nsrip-dd in #1466
• ddtrace/tracer: switch atomics to 32 bits by @knusbaum in #1443
• ddtrace/tracer: better trace and span ID randomness by @ajgajg1134 in #1472
• ddtrace: support tracer.SetUser on a mockspan by @Julio-Guerra in #1480

Database Monitoring

• contrib/sql/driver: trace sql queries from database drivers implementing DriverContext by @david-ds in #1502

Application Security Monitoring (ASM)

• appsec: fix stripping on macOS by @Julio-Guerra in #1481
• appsec: add support for linux/arm64 and darwin/arm64 by @Julio-Guerra in #1494

Profiler

• Cap the CPU profile duration so it doesn't exceed the profiling period (#1486)
• Ensure that CPU profile records profiler work (#1485)

Full Changelog: v1.42.1...v1.43.0