@spatius/avatarkit 1.3.7 → 1.3.9

package/dist/internal-telemetry.d.ts

@@ -11,11 +11,6 @@ import { Attributes } from '@opentelemetry/api';
  * @param mono - the `performance.now()` value recorded at collection time
  */
 export declare function resolveMonoTimestamp(mono: number): number;
-/**
- * Whether clock calibration against the backend has completed. Timestamps
- * resolve either way; this only reports whether they are server-aligned yet.
- */
-export declare function isClockCalibrated(): boolean;
 /**
  * Handle for one round's trace.
  *
@@ -80,23 +75,22 @@ export declare function peekTraceparent(rawMessage: Uint8Array): string | undefi
  */
 export declare function recordMetric(name: string, value: number, attributes?: Attributes): void;
 /**
- * The client environment fields this SDK stamps on every OTel log record —
- * `host`, `domain`, `url`, `pathname`, `referrer`, `user_agent`, `locale`,
- * screen/viewport size and `timezone`.
+ * Emit one event onto avatarkit's OTel log channel.
+ *
+ * Must go through here rather than the RTC SDK calling `logs.getLogger().emit()`
+ * itself. Sharing the global LoggerProvider only carries Resource-level
+ * attributes (app_id / region / sdk.version); the record-level identity fields
+ * — `user_id`, `client_id` — are stamped inside this SDK's emit path, so a
+ * record emitted directly through the provider carries none of them. Routing
+ * through here is what the Android / iOS RTC SDKs already do via their
+ * `RTCTelemetry.track` entry, and it additionally picks up crash-replay
+ * persistence and the pre-calibration queue.
  *
- * Shared with the RTC SDK rather than re-derived there. These are record-level
- * fields, not Resource attributes: they are read from `window.location` at emit
- * time because `url`/`pathname` change as a single-page app routes. Sharing the
- * OTel providers therefore does not carry them across — the RTC SDK emits
- * through its own logger and would report no `host` at all, which is what
- * prompted this export. Re-implementing the collection on that side would let
- * the two drift apart in field names and in how each value is read, and the
- * backend aggregates on exactly these names.
- *
- * Call at emit time, once per record; spread the result before the caller's own
- * properties so an explicit value at the call site still wins.
+ * The timestamp is taken here rather than accepted from the caller: this path
+ * resolves it against the calibrated clock and stamps `server_timestamp`
+ * alongside, which a caller-supplied `Date.now()` cannot do.
  */
-export declare function clientContextFields(): Record<string, string | number>;
+export declare function trackEvent(event: string, level?: 'debug' | 'info' | 'warning' | 'error', contents?: Record<string, unknown>): void;
 /**
  * Declare which SDK these records come from, as the `sdk.package` and
  * `sdk.version` resource attributes.
@@ -124,3 +118,15 @@ export declare function setSdkIdentity(identity: {
     sdkPackage?: string;
     sdkVersion?: string;
 }): void;
+/**
+ * The client environment fields this SDK stamps on every OTel log record —
+ * `host`, `domain`, `url`, `pathname`, `referrer`, `user_agent`, `locale`,
+ * screen/viewport size and `timezone`.
+ *
+ * **Kept only for `@spatius/avatarkit-rtc` ≤ 1.1.3**, which imports it from this
+ * entry (RTC ≥ 1.1.4 routes through {@link trackEvent}, which stamps these fields
+ * itself, and no longer calls this). RTC's peer range is `>=1.3.7`, so a host
+ * still on 1.1.3 that upgrades this package would otherwise hit an undefined
+ * import. Remove once no 1.1.3 hosts remain in telemetry.
+ */
+export declare function clientContextFields(): Record<string, string | number>;

package/dist/internal-telemetry.js

@@ -1,4 +1,4 @@
-import { A as clockSync, I as recordMetric$1, o as startPlaybackTrace$1, u as Message, y as clientContextFields$1, z as setSdkIdentity$1 } from "./otel-trace-Y_BtH06z.js";
+import { F as recordMetric$1, R as setSdkIdentity$1, T as trackEventOtel, g as clientContextFields$1, k as clockSync, o as startPlaybackTrace$1, u as Message } from "./otel-trace-DqXSWBaw.js";
 //#region internal-telemetry.ts
 /**
 * Internal telemetry surface for the companion RTC SDK.
@@ -35,13 +35,6 @@ function resolveMonoTimestamp(mono) {
 	return clockSync.resolveMono(mono);
 }
 /**
-* Whether clock calibration against the backend has completed. Timestamps
-* resolve either way; this only reports whether they are server-aligned yet.
-*/
-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
@@ -91,24 +84,23 @@ function recordMetric(name, value, attributes = {}) {
 	recordMetric$1(name, value, attributes);
 }
 /**
-* The client environment fields this SDK stamps on every OTel log record —
-* `host`, `domain`, `url`, `pathname`, `referrer`, `user_agent`, `locale`,
-* screen/viewport size and `timezone`.
-*
-* Shared with the RTC SDK rather than re-derived there. These are record-level
-* fields, not Resource attributes: they are read from `window.location` at emit
-* time because `url`/`pathname` change as a single-page app routes. Sharing the
-* OTel providers therefore does not carry them across — the RTC SDK emits
-* through its own logger and would report no `host` at all, which is what
-* prompted this export. Re-implementing the collection on that side would let
-* the two drift apart in field names and in how each value is read, and the
-* backend aggregates on exactly these names.
-*
-* Call at emit time, once per record; spread the result before the caller's own
-* properties so an explicit value at the call site still wins.
+* Emit one event onto avatarkit's OTel log channel.
+*
+* Must go through here rather than the RTC SDK calling `logs.getLogger().emit()`
+* itself. Sharing the global LoggerProvider only carries Resource-level
+* attributes (app_id / region / sdk.version); the record-level identity fields
+* — `user_id`, `client_id` — are stamped inside this SDK's emit path, so a
+* record emitted directly through the provider carries none of them. Routing
+* through here is what the Android / iOS RTC SDKs already do via their
+* `RTCTelemetry.track` entry, and it additionally picks up crash-replay
+* persistence and the pre-calibration queue.
+*
+* The timestamp is taken here rather than accepted from the caller: this path
+* resolves it against the calibrated clock and stamps `server_timestamp`
+* alongside, which a caller-supplied `Date.now()` cannot do.
 */
-function clientContextFields() {
-	return clientContextFields$1();
+function trackEvent(event, level = "info", contents = {}) {
+	trackEventOtel(event, level, contents);
 }
 /**
 * Declare which SDK these records come from, as the `sdk.package` and
@@ -136,5 +128,19 @@ function clientContextFields() {
 function setSdkIdentity(identity) {
 	setSdkIdentity$1(identity);
 }
+/**
+* The client environment fields this SDK stamps on every OTel log record —
+* `host`, `domain`, `url`, `pathname`, `referrer`, `user_agent`, `locale`,
+* screen/viewport size and `timezone`.
+*
+* **Kept only for `@spatius/avatarkit-rtc` ≤ 1.1.3**, which imports it from this
+* entry (RTC ≥ 1.1.4 routes through {@link trackEvent}, which stamps these fields
+* itself, and no longer calls this). RTC's peer range is `>=1.3.7`, so a host
+* still on 1.1.3 that upgrades this package would otherwise hit an undefined
+* import. Remove once no 1.1.3 hosts remain in telemetry.
+*/
+function clientContextFields() {
+	return clientContextFields$1();
+}
 //#endregion
-export { clientContextFields, isClockCalibrated, peekTraceparent, recordMetric, resolveMonoTimestamp, setSdkIdentity, startPlaybackTrace };
+export { clientContextFields, peekTraceparent, recordMetric, resolveMonoTimestamp, setSdkIdentity, startPlaybackTrace, trackEvent };