@interopio/otel 0.1.17 → 0.1.19

package/insights.d.ts

@@ -1392,6 +1392,18 @@ export namespace IOInsights {
      * the pre-init recorder (when installed) captures errors from page start -
      * opt out of that with the configuration object's `preInit: false`.
      *
+     * Also works in NodeJS, via process.uncaughtExceptionMonitor - a
+     * behavior-preserving hook: the process still crashes exactly as it would
+     * have. The span processors are force-flushed immediately, so the crash
+     * span is exported whenever anything keeps the process alive past the
+     * crash (an application 'uncaughtException' handler, a graceful
+     * shutdown); on a hard crash the export cannot complete and the span is
+     * lost with the process. Under Node's default
+     * unhandled-rejections=throw mode, crash-grade unhandled rejections are
+     * reported too; non-crashing rejection observation is deliberately not
+     * done in Node, because subscribing to process.unhandledRejection would
+     * suppress Node's default crash semantics.
+     *
      * @default false
      */
     instrumentErrors?: boolean | ErrorInstrumentationConfig;
@@ -1440,7 +1452,18 @@ export namespace IOInsights {
 
     /**
      * If `true`, io.Insights will instrument and trace the application startup process
-     * automatically.
+     * automatically: a root "interopio.api.appStartup" span starting at the runtime's
+     * time origin, under which spans created during the startup window are nested
+     * (via the propagation defaults). In browsers the root carries child spans and
+     * KPIs reconstructed from the performance timeline (navigation phases, paints,
+     * long tasks, startup-window web vitals, lifecycle transitions).
+     *
+     * Also works in NodeJS: the root span opens at process start and the startup
+     * window nesting applies, but the browser performance-timeline children are
+     * not produced. The window closes on startupParentSpanTimeoutMs or an explicit
+     * startupTraceFinished() call ("loader" mode behaves as "any" in Node - there
+     * is no loader signal). When the platform provides a root propagation info,
+     * the startup span is parented under it.
      *
      * @default true
      */
@@ -1450,7 +1473,7 @@ export namespace IOInsights {
      * If `true`, io.Insights will instrument and trace the application initialization process
      * automatically.
      *
-     * @default true
+     * @default false
      * @deprecated use instrumentAppStartup
      */
     instrumentAppLoad?: boolean;
@@ -1459,7 +1482,7 @@ export namespace IOInsights {
      * If `true`, io.Insights will instrument and trace the steps of the document load
      * process automatically
      *
-     * @default true
+     * @default false
      * @deprecated use instrumentAppStartup
      */
     instrumentDocumentLoad?: boolean;
@@ -1579,9 +1602,12 @@ export namespace IOInsights {
     /**
      * If non-zero, how long after application startup will any traced operations
      * automatically be nested under the application startup trace. The timeout is counted from the moment
-     * the io.Connect API begins initializing.
-     * 
-     * @default 0
+     * the io.Connect API begins initializing. Without a timeout the startup window
+     * only closes on an explicit startupTraceFinished() call (or the loader signal
+     * in io.Connect Desktop windows) - the root span stays open, and unexported,
+     * until then.
+     *
+     * @default 3000
      */
     startupParentSpanTimeoutMs?: number;
     /**
@@ -1591,7 +1617,10 @@ export namespace IOInsights {
      * * timeout - same as "explicit" OR when startupParentSpanTimeoutMs have elapsed and the DOMContentLoaded event has fired
      * * loader - same as "explicit" OR when the loading animation of the window has completed
      * * any - when any of the above conditions are met
-     * 
+     *
+     * In NodeJS there is no loader signal (or DOM readiness): "loader" behaves as
+     * "any", and the timeout counts alone.
+     *
      * @default "any"
      */
     startupParentSpanEnd?: "explicit" | "timeout" | "loader" | "any";
@@ -2859,6 +2888,18 @@ export namespace IOInsights {
      * @default 0
      */
     chainLength?: number;
+    /**
+     * Unless `false`, focus spans for windows that sit in a workspace also
+     * carry the workspace context - workspaceId, workspaceName and
+     * workspaceTitle. Only workspace membership is resolvable synchronously;
+     * the id/name/title are fetched from the workspaces frame asynchronously
+     * (two round trips per focus change into a workspace window) and added to
+     * the still-open focus span when they arrive - a focus change racing the
+     * lookup loses only these attributes.
+     *
+     * @default true
+     */
+    includeWorkspaceInfo?: boolean;
   }
 
   /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@interopio/otel",
-  "version": "0.1.17",
+  "version": "0.1.19",
   "description": "io.Insights observability library",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",