libdatadog 40.0.0.2.0 → 44.0.1.1.0

data/vendor/{libdatadog-40.0.0/aarch64-linux-musl → libdatadog-44.0.1/arm64-darwin}/include/datadog/data-pipeline.h

@@ -187,19 +187,21 @@ struct ddog_TraceExporterError *ddog_trace_exporter_config_set_shared_runtime(st
                                                                               struct ddog_ForkSafeRuntime *handle);
 
 /**
- * Enables OTLP HTTP/JSON export and sets the endpoint URL.
+ * Enables OTLP trace export and sets the endpoint URL.
  *
- * When set, traces are sent to this URL in OTLP HTTP/JSON format instead of the Datadog
- * agent. The host language is responsible for resolving the endpoint from its configuration
- * (e.g. `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`) before calling this function.
+ * When set, traces are sent to this URL using the protocol selected by
+ * `ddog_trace_exporter_config_set_otlp_protocol` instead of the Datadog agent. The host language
+ * is responsible for resolving the endpoint from its configuration (e.g.
+ * `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`) before calling this function.
  */
 struct ddog_TraceExporterError *ddog_trace_exporter_config_set_otlp_endpoint(struct ddog_TraceExporterConfig *config,
                                                                              ddog_CharSlice url);
 
 /**
- * Sets the OTLP export protocol. Accepts the OTel-standard values `http/json` (default) or
- * `http/protobuf`; `grpc` is rejected as not yet supported. The host language resolves the value
+ * Sets the OTLP export protocol. Accepts the OTel-standard values `http/json` (default),
+ * `http/protobuf`, or `grpc`; unknown values are rejected. The host language resolves the value
  * (e.g. from `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL`).
+ * The `grpc` protocol currently supports plaintext `http://` endpoints only.
  *
  * Has no effect unless an OTLP endpoint is also configured via
  * `ddog_trace_exporter_config_set_otlp_endpoint`; without one, traces are sent to the
@@ -240,6 +242,48 @@ struct ddog_TraceExporterError *ddog_trace_exporter_config_set_stats_cardinality
  */
 struct ddog_CardinalityLimitConfig ddog_trace_exporter_config_default_stats_cardinality_limit(void);
 
+/**
+ * Enables agentless APM trace export and sets the intake URL and API key.
+ *
+ * When set, APM trace spans are sent directly to the Datadog HTTP intake in JSON format
+ * (`POST /v1/input`) instead of through the Datadog Agent. Agentless trace export is mutually
+ * exclusive with both an agent URL ([`ddog_trace_exporter_config_set_url`]) and an OTLP endpoint
+ * ([`ddog_trace_exporter_config_set_otlp_endpoint`]); combining either with this setter causes
+ * [`ddog_trace_exporter_new`] to return an error.
+ */
+struct ddog_TraceExporterError *ddog_trace_exporter_config_set_agentless_endpoint(struct ddog_TraceExporterConfig *config,
+                                                                                  ddog_CharSlice url,
+                                                                                  ddog_CharSlice api_key);
+
+/**
+ * Sets the request timeout (in milliseconds) used by the agentless intake transport.
+ *
+ * Defaults to 15 seconds when unset. Calling this without also setting an agentless endpoint
+ * causes [`ddog_trace_exporter_new`] to return an error.
+ */
+struct ddog_TraceExporterError *ddog_trace_exporter_config_set_agentless_timeout(struct ddog_TraceExporterConfig *config,
+                                                                                 uint64_t timeout_ms);
+
+/**
+ * Sets the span obfuscation configuration from a JSON string.
+ *
+ * `json` is deserialized into `ObfuscationConfig` (the same struct the Datadog Agent uses),
+ * which controls obfuscation of HTTP URLs, SQL resources, Redis/Valkey commands, memcached
+ * commands, credit-card numbers, elasticsearch/opensearch/mongodb bodies, and tag-replace
+ * rules. Obfuscation is applied to every span on the agentless export path (see
+ * [`ddog_trace_exporter_config_set_agentless_endpoint`]); it has no effect on the agent path.
+ *
+ * Returns an error if `json` is not valid UTF-8 or fails to deserialize. Example:
+ * ```c
+ * ddog_trace_exporter_config_set_obfuscation_config(
+ *   cfg, DDOG_CHARSLICE_C(
+ *     "{\"http\":{\"remove_query_string\":true},"
+ *     "\"credit_cards\":{\"enabled\":true}}"));
+ * ```
+ */
+struct ddog_TraceExporterError *ddog_trace_exporter_config_set_obfuscation_config(struct ddog_TraceExporterConfig *config,
+                                                                                  ddog_CharSlice json);
+
 /**
  * Configure the exporter to write traces as newline-delimited JSON to stdout (the Datadog
  * Forwarder "log exporter" path) instead of sending them to a Datadog agent. Used in serverless
@@ -262,9 +306,9 @@ struct ddog_TraceExporterError *ddog_trace_exporter_config_set_output_to_log(str
 /**
  * Create a new TraceExporter instance.
  *
- * When an OTLP endpoint is configured via `TraceExporterConfig`, the exporter sends traces to
- * that endpoint in OTLP over HTTP — JSON or protobuf per the configured protocol — instead of
- * to the Datadog agent. The same payload (e.g. MessagePack) is passed to
+ * When an OTLP endpoint is configured via `TraceExporterConfig`, the exporter sends traces using
+ * the configured `http/json`, `http/protobuf`, or `grpc` protocol instead of the Datadog agent.
+ * The same payload (e.g. MessagePack) is passed to
  * `ddog_trace_exporter_send`; the library decodes and converts it to OTLP when OTLP is enabled.
  *
  * # Arguments

data/vendor/{libdatadog-40.0.0 → libdatadog-44.0.1}/arm64-darwin/include/datadog/ffe.h

@@ -147,6 +147,18 @@ struct ddog_ffe_Result_HandleConfiguration ddog_ffe_configuration_new(struct ddo
  */
 void ddog_ffe_configuration_drop(ddog_ffe_Handle_Configuration *config);
 
+/**
+ * Get the config-level `observeFullEvaluationData` flag.
+ *
+ * Opt-in boolean for emitting full flag evaluation data from SDKs to Datadog. Flag evaluation data
+ * may contain PII; defaults to `false` for privacy.
+ *
+ * # Safety
+ *
+ * `config` must be a valid `Configuration` handle created by `ddog_ffe_configuration_new`.
+ */
+bool ddog_ffe_configuration_get_observe_full_evaluation_data(ddog_ffe_Handle_Configuration config);
+
 /**
  * Creates a new EvaluationContext with the given targeting key and attributes.
  *

data/vendor/{libdatadog-40.0.0/aarch64-linux → libdatadog-44.0.1/arm64-darwin}/include/datadog/otel-thread-ctx.h

@@ -79,6 +79,22 @@ void ddog_otel_thread_ctx_update(const uint8_t (*trace_id)[16],
                                  uint8_t trace_flags,
                                  const uint8_t (*local_root_span_id)[8]);
 
+/**
+ * Update `ctx` and attach it to the current thread. Returns the previously attached different
+ * context, if any.
+ *
+ * # Safety
+ *
+ * `ctx` may be null; otherwise it must be a valid non-null pointer obtained from this API.
+ * If attached, it must be attached only to the calling native thread and must not be
+ * concurrently updated or freed. A non-null returned context is owned by the caller.
+ */
+struct ddog_ThreadContextHandle *ddog_otel_thread_ctx_update_and_attach(struct ddog_ThreadContextHandle *ctx,
+                                                                        const uint8_t (*trace_id)[16],
+                                                                        const uint8_t (*span_id)[8],
+                                                                        uint8_t trace_flags,
+                                                                        const uint8_t (*local_root_span_id)[8]);
+
 #ifdef __cplusplus
 }  // extern "C"
 #endif  // __cplusplus

data/vendor/{libdatadog-40.0.0/x86_64-linux-musl → libdatadog-44.0.1/arm64-darwin}/lib/pkgconfig/datadog_profiling_with_rpath.pc

@@ -8,7 +8,7 @@ includedir=${prefix}/include
 
 Name: datadog_profiling
 Description: Contains common code used to implement Datadog's Continuous Profilers. (Dynamic linking variant, sets rpath)
-Version: 40.0.0
+Version: 44.0.1
 Requires:
 Libs: -L${libdir} -ldatadog_profiling -Wl,-rpath,${libdir}
 Libs.private: