0.5.0

Breaking Changes

• dd_rum_start_view_obj() and dd_rum_stop_view_obj() functions have been removed. Use dd_rum_start_view() and dd_rum_stop_view() instead.
• datadog::CoreConfig::SetApplicationVersion() is renamed to datadog::CoreConfig::SetVersion() (and dd_core_config_set_application_version() is now dd_core_config_set_version()).
• The datadog_install() CMake convenience function now requires keyword arguments RUNTIME_DESTINATION and LIBRARY_DESTINATION. Replace datadog_install(bin) with datadog_install(RUNTIME_DESTINATION bin).

Features

• Pre-built macOS release artifacts are now universal binaries containing both arm64 and x86_64 slices.
• Added support for the us2-fed site.

Fixes

• datadog_install() now automatically deploys the SDK shared library alongside the application and configures the correct runtime search path (RPATH) on POSIX platforms.
• Strings passed as name or key to the RUM Operations API are now safely copied, preventing potential crashes or undefined behavior if the original string is destroyed or modified after the call returns.
• Fixed compilation errors when building for 32-bit ARMv7 targets caused by C++ type-deduction issues.

0.4.0

Breaking Changes

• When recording a log message via dd_logger_<level>() or datadog::Logger::<Level>(), the API allows an err parameter to be passed regardless of log level.
• The err value passed in log calls now accepts a message string, which will be included in resulting log and RUM events as error.message.

Fixes

• When a logger forwards error details to RUM, RUM now correctly populates error.message from the error message rather than the log message text.

0.3.0

Note

Initial preview release of the Datadog C++ SDK.
While at v0, breaking API changes may be introduced in minor-version releases.

Features

• The SDK may be incorporated into an existing CMake project via FetchContent or find_package.
• APIs are available for both C and C++.
• The SDK may be configured and initialized via datadog::Core or dd_core_t.
• Diagnostic output will be written to stderr by default; use SetDiagnosticHandler() to reroute or suppress this output.
• Transient data will be stored under .datadog/ in the working directory; use SetApplicationStoragePath() to configure an explicit path that's unique to your application.
• Support for user tracking consent is fully implemented: data will not be stored when consent is revoked, and data will only be uploaded once consent is granted.
• Use the RUM feature to track views, actions, resources, errors, and operations.
• Use the Logging feature to send remote log messages to Datadog.
• Use the Crash Reporting feature to detect crashes and report them as RUM Errors on next launch.