@spatius/avatarkit 1.3.1-beta.6 → 1.3.1

package/dist/internal-telemetry.js

@@ -1,4 +1,5 @@
-import { h as clockSync } from "./logger-fAU8oahT.js";
+import { C as recordMetric$1, g as clockSync } from "./logger-BOpQ7u0w.js";
+import { a as startPlaybackTrace$1 } from "./otel-trace-Ct4T48nC.js";
 //#region internal-telemetry.ts
 /**
 * Internal telemetry surface for the companion RTC SDK.
@@ -41,5 +42,29 @@ function resolveMonoTimestamp(mono) {
 function isClockCalibrated() {
 	return clockSync.isReady();
 }
+/**
+* Open one round's trace: `driven.request` → `playback` → the caller's spans.
+*
+* Shared with the RTC SDK rather than reimplemented there, so both packages
+* emit the same tree. The root's ids derive from the conversation id, which is
+* what lets the backend's spans join a round without threading state through;
+* reproducing that separately would mean two definitions of one wire contract.
+*/
+function startPlaybackTrace(conversationId, startTimeMs, attrs = {}) {
+	return startPlaybackTrace$1(conversationId, startTimeMs, attrs);
+}
+/**
+* Record one measurement onto avatarkit's metric pipeline.
+*
+* Must go through here rather than the RTC SDK reaching for the global meter
+* itself: a metrics export is skipped entirely unless that round carried real
+* business data, and the flag saying so lives in this module. A histogram
+* written directly through the global provider lands in the same instrument but
+* leaves the flag clear, so the whole batch — RTC's readings included — is
+* dropped before it is sent.
+*/
+function recordMetric(name, value, attributes = {}) {
+	recordMetric$1(name, value, attributes);
+}
 //#endregion
-export { isClockCalibrated, resolveMonoTimestamp };
+export { isClockCalibrated, recordMetric, resolveMonoTimestamp, startPlaybackTrace };