autotel 6.2.1 → 6.3.0

package/dist/{init-BHp-kqLJ.d.ts → init-C1i2_2zl.d.ts}

@@ -222,7 +222,7 @@ interface ProcessHandlersConfig {
   shutdownTimeoutMs?: number;
 }
 //#endregion
-//#region src/init.d.ts
+//#region src/otlp-exporters.d.ts
 type OtlpSignal = 'traces' | 'metrics' | 'logs';
 interface OtlpDestinationConfig {
   /**
@@ -254,6 +254,8 @@ interface OtlpDestinationConfig {
  * exactly like emitting no telemetry at all.
  */
 type AutotelProtocol = 'http' | 'http/protobuf' | 'grpc';
+//#endregion
+//#region src/autotel-config.d.ts
 interface AutotelConfig {
   /** Service name (required) */
   service: string;
@@ -266,6 +268,24 @@ interface AutotelConfig {
    * process lifecycle management to the application.
    */
   processHandlers?: boolean | ProcessHandlersConfig;
+  /**
+   * Flush telemetry when the process finishes on its own. Default: `true`.
+   *
+   * `processHandlers` covers a process that is stopped or that crashes. Neither
+   * of those fires when a script runs to completion: Node drains the event loop
+   * and exits, and anything the batch span processor is still holding goes with
+   * it. Autotel listens for `beforeExit` and flushes there, so a CLI, a cron
+   * job or a CI step keeps its telemetry without calling `shutdown()`.
+   *
+   * A flush, not a shutdown: `beforeExit` fires on any event-loop drain, so a
+   * process that resumes work keeps working telemetry. Bounded by
+   * `processHandlers.shutdownTimeoutMs`, after which the process exits rather
+   * than waiting on an exporter that never answers.
+   *
+   * Set to `false` if your process manages its own exit and you would rather
+   * autotel added no listener.
+   */
+  flushOnExit?: boolean;
   /**
    * Local developer UX for autotel-devtools.
    *
@@ -1166,6 +1186,8 @@ interface AutotelConfig {
    */
   minLevel?: 'debug' | 'info' | 'warn' | 'error';
 }
+//#endregion
+//#region src/init.d.ts
 /**
  * Lock the logger to prevent further `init()` calls.
  * Use this when framework plugins set up instrumentation and you want
@@ -1243,4 +1265,4 @@ declare function init(cfg: AutotelConfig): void;
  */
 declare function isInitialized(): boolean;
 //#endregion
-export { isLoggerLocked as a, StringRedactor as c, isInitialized as i, createStringRedactor as l, OtlpSignal as n, lockLogger as o, init as r, ProcessHandlersConfig as s, AutotelConfig as t };
+export { AutotelConfig as a, StringRedactor as c, lockLogger as i, createStringRedactor as l, isInitialized as n, OtlpSignal as o, isLoggerLocked as r, ProcessHandlersConfig as s, init as t };

package/dist/{init-BoIYyB6Q.d.cts → init-CfVWN4ND.d.cts}

@@ -222,7 +222,7 @@ interface ProcessHandlersConfig {
   shutdownTimeoutMs?: number;
 }
 //#endregion
-//#region src/init.d.ts
+//#region src/otlp-exporters.d.ts
 type OtlpSignal = 'traces' | 'metrics' | 'logs';
 interface OtlpDestinationConfig {
   /**
@@ -254,6 +254,8 @@ interface OtlpDestinationConfig {
  * exactly like emitting no telemetry at all.
  */
 type AutotelProtocol = 'http' | 'http/protobuf' | 'grpc';
+//#endregion
+//#region src/autotel-config.d.ts
 interface AutotelConfig {
   /** Service name (required) */
   service: string;
@@ -266,6 +268,24 @@ interface AutotelConfig {
    * process lifecycle management to the application.
    */
   processHandlers?: boolean | ProcessHandlersConfig;
+  /**
+   * Flush telemetry when the process finishes on its own. Default: `true`.
+   *
+   * `processHandlers` covers a process that is stopped or that crashes. Neither
+   * of those fires when a script runs to completion: Node drains the event loop
+   * and exits, and anything the batch span processor is still holding goes with
+   * it. Autotel listens for `beforeExit` and flushes there, so a CLI, a cron
+   * job or a CI step keeps its telemetry without calling `shutdown()`.
+   *
+   * A flush, not a shutdown: `beforeExit` fires on any event-loop drain, so a
+   * process that resumes work keeps working telemetry. Bounded by
+   * `processHandlers.shutdownTimeoutMs`, after which the process exits rather
+   * than waiting on an exporter that never answers.
+   *
+   * Set to `false` if your process manages its own exit and you would rather
+   * autotel added no listener.
+   */
+  flushOnExit?: boolean;
   /**
    * Local developer UX for autotel-devtools.
    *
@@ -1166,6 +1186,8 @@ interface AutotelConfig {
    */
   minLevel?: 'debug' | 'info' | 'warn' | 'error';
 }
+//#endregion
+//#region src/init.d.ts
 /**
  * Lock the logger to prevent further `init()` calls.
  * Use this when framework plugins set up instrumentation and you want
@@ -1243,4 +1265,4 @@ declare function init(cfg: AutotelConfig): void;
  */
 declare function isInitialized(): boolean;
 //#endregion
-export { isLoggerLocked as a, StringRedactor as c, isInitialized as i, createStringRedactor as l, OtlpSignal as n, lockLogger as o, init as r, ProcessHandlersConfig as s, AutotelConfig as t };
+export { AutotelConfig as a, StringRedactor as c, lockLogger as i, createStringRedactor as l, isInitialized as n, OtlpSignal as o, isLoggerLocked as r, ProcessHandlersConfig as s, init as t };