@btravstack/observability 0.5.0 → 0.7.0

package/dist/index.cjs

@@ -1,9 +1,9 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 let _btravstack_config = require("@btravstack/config");
 let _btravstack_core = require("@btravstack/core");
-let unthrown = require("unthrown");
 let _btravstack_di = require("@btravstack/di");
 //#region src/config.ts
+const isLevel = (value) => _btravstack_core.LEVELS.includes(value);
 /**
 * `LOG_LEVEL`, as a `ConfigField` of the six levels and nothing else.
 *
@@ -18,7 +18,7 @@ const logLevel = (options = {}) => {
 	const text = _btravstack_config.Config.string("LOG_LEVEL", { default: options.default ?? "info" });
 	return {
 		variable: text.variable,
-		parse: (raw) => text.parse(raw).flatMap((value) => _btravstack_core.LEVELS.includes(value) ? (0, unthrown.Ok)(value) : (0, unthrown.Err)(new _btravstack_config.ConfigFieldInvalid({ reason: `must be one of ${_btravstack_core.LEVELS.join(", ")}, got ${JSON.stringify(value)}` })))
+		parse: (raw) => text.parse(raw).ensure(isLevel, (value) => new _btravstack_config.ConfigFieldInvalid({ reason: `must be one of ${_btravstack_core.LEVELS.join(", ")}, got ${JSON.stringify(value)}` }))
 	};
 };
 /** The schema `observability()` binds `LoggerConfig` through — one field today, and the place a second one lands. */

package/dist/index.mjs

@@ -1,8 +1,8 @@
 import { Config, ConfigFieldInvalid, Env } from "@btravstack/config";
 import { LEVELS, Logger, currentUnit } from "@btravstack/core";
-import { Err, Ok } from "unthrown";
 import { Module, Port, Provider } from "@btravstack/di";
 //#region src/config.ts
+const isLevel = (value) => LEVELS.includes(value);
 /**
 * `LOG_LEVEL`, as a `ConfigField` of the six levels and nothing else.
 *
@@ -17,7 +17,7 @@ const logLevel = (options = {}) => {
 	const text = Config.string("LOG_LEVEL", { default: options.default ?? "info" });
 	return {
 		variable: text.variable,
-		parse: (raw) => text.parse(raw).flatMap((value) => LEVELS.includes(value) ? Ok(value) : Err(new ConfigFieldInvalid({ reason: `must be one of ${LEVELS.join(", ")}, got ${JSON.stringify(value)}` })))
+		parse: (raw) => text.parse(raw).ensure(isLevel, (value) => new ConfigFieldInvalid({ reason: `must be one of ${LEVELS.join(", ")}, got ${JSON.stringify(value)}` }))
 	};
 };
 /** The schema `observability()` binds `LoggerConfig` through — one field today, and the place a second one lands. */

package/dist/otel.cjs

@@ -1,24 +1,10 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 let _btravstack_core = require("@btravstack/core");
-let unthrown = require("unthrown");
 let _btravstack_di = require("@btravstack/di");
 let _opentelemetry_api = require("@opentelemetry/api");
 let _opentelemetry_sdk_node = require("@opentelemetry/sdk-node");
+let unthrown = require("unthrown");
 //#region src/otel.ts
-/**
-* The tracing half of observability — the ADAPTER, not the contract. `Tracer`
-* and `Meter` are the kernel's ports, and OTel's presence stops at this subpath,
-* behind an optional peer exactly like `pino`.
-*
-* The ports are narrowings of OTel's own shapes, so what the SDK hands back
-* satisfies them with no translation in between.
-*/
-/**
-* The SDK itself, module-private: providing it is what starts it, and `release`
-* is what flushes it. It rides the graph as a RESOURCE so the kernel closes it
-* on every exit path — a span lost in `shutdown()` becomes a `teardownError` and
-* exit `2`, never silence.
-*/
 var OtelSdk = class extends (0, _btravstack_di.Port)("OtelSdk") {};
 /**
 * The OTel starter: a module providing `Tracer` and `Meter` over a `NodeSDK`
@@ -33,15 +19,32 @@ var OtelSdk = class extends (0, _btravstack_di.Port)("OtelSdk") {};
 * **Auto-instrumentation cannot live here**: the register hook must be
 * preloaded before the instrumented libraries are imported, which no DI
 * provider can promise. Preloading is the deployment's line.
+*
+* **What CAN live here is a starter's own instrumentation.** Every package
+* that contributed to `Instrumentations` is loaded and handed to the SDK, so
+* composing a starter is what declares the instrumentation and composing this
+* is what turns it on. A contribution whose optional peer is not installed
+* loads as `undefined` and is dropped — the contributor says so at `debug`,
+* since it is the one that knows why.
+*
+* The module contributes one member of its own, which loads nothing. That is
+* what makes `Instrumentations` a port the graph always has — a collector
+* depending on a set port NOTHING provides is an unmet dependency, both at
+* plan time and in `Needs`. Guice's `newSetBinder` declares the empty set for
+* the same reason.
 */
 const otel = (options) => (0, _btravstack_di.Module)("Otel")({
 	provides: [
-		(0, _btravstack_di.Provider)(OtelSdk)({
-			acquire: () => {
-				const sdk = new _opentelemetry_sdk_node.NodeSDK(options);
+		_btravstack_di.Provider.member(_btravstack_core.Instrumentations)({ value: () => Promise.resolve(void 0) }),
+		(0, _btravstack_di.Provider)(OtelSdk)({ offered: _btravstack_core.Instrumentations }, {
+			acquire: ({ offered }) => (0, unthrown.fromSafePromise)(Promise.all(offered.map((load) => load())).then((loaded) => {
+				const sdk = new _opentelemetry_sdk_node.NodeSDK({
+					...options,
+					instrumentations: [...options?.instrumentations ?? [], ...loaded.filter((one) => one !== void 0)]
+				});
 				sdk.start();
-				return (0, unthrown.Ok)(sdk);
-			},
+				return sdk;
+			})),
 			release: (sdk) => sdk.shutdown()
 		}),
 		(0, _btravstack_di.Provider)(_btravstack_core.Tracer)({ sdk: OtelSdk }, { sync: () => {

package/dist/otel.d.cts

@@ -15,6 +15,19 @@ import { NodeSDKConfiguration } from "@opentelemetry/sdk-node";
  * **Auto-instrumentation cannot live here**: the register hook must be
  * preloaded before the instrumented libraries are imported, which no DI
  * provider can promise. Preloading is the deployment's line.
+ *
+ * **What CAN live here is a starter's own instrumentation.** Every package
+ * that contributed to `Instrumentations` is loaded and handed to the SDK, so
+ * composing a starter is what declares the instrumentation and composing this
+ * is what turns it on. A contribution whose optional peer is not installed
+ * loads as `undefined` and is dropped — the contributor says so at `debug`,
+ * since it is the one that knows why.
+ *
+ * The module contributes one member of its own, which loads nothing. That is
+ * what makes `Instrumentations` a port the graph always has — a collector
+ * depending on a set port NOTHING provides is an unmet dependency, both at
+ * plan time and in `Needs`. Guice's `newSetBinder` declares the empty set for
+ * the same reason.
  */
 declare const otel: (options?: Partial<NodeSDKConfiguration>) => Module<Tracer | Meter, never, Scope>;
 declare const UnitSpan_base: import("@btravstack/di").PortClass<"UnitSpan">;

package/dist/otel.d.mts

@@ -15,6 +15,19 @@ import { NodeSDKConfiguration } from "@opentelemetry/sdk-node";
  * **Auto-instrumentation cannot live here**: the register hook must be
  * preloaded before the instrumented libraries are imported, which no DI
  * provider can promise. Preloading is the deployment's line.
+ *
+ * **What CAN live here is a starter's own instrumentation.** Every package
+ * that contributed to `Instrumentations` is loaded and handed to the SDK, so
+ * composing a starter is what declares the instrumentation and composing this
+ * is what turns it on. A contribution whose optional peer is not installed
+ * loads as `undefined` and is dropped — the contributor says so at `debug`,
+ * since it is the one that knows why.
+ *
+ * The module contributes one member of its own, which loads nothing. That is
+ * what makes `Instrumentations` a port the graph always has — a collector
+ * depending on a set port NOTHING provides is an unmet dependency, both at
+ * plan time and in `Needs`. Guice's `newSetBinder` declares the empty set for
+ * the same reason.
  */
 declare const otel: (options?: Partial<NodeSDKConfiguration>) => Module<Tracer | Meter, never, Scope>;
 declare const UnitSpan_base: import("@btravstack/di").PortClass<"UnitSpan">;

package/dist/otel.mjs

@@ -1,23 +1,9 @@
-import { Meter, Tracer, currentUnit } from "@btravstack/core";
-import { Ok } from "unthrown";
+import { Instrumentations, Meter, Tracer, currentUnit } from "@btravstack/core";
 import { Module, Port, Provider } from "@btravstack/di";
 import { metrics, trace } from "@opentelemetry/api";
 import { NodeSDK } from "@opentelemetry/sdk-node";
+import { fromSafePromise } from "unthrown";
 //#region src/otel.ts
-/**
-* The tracing half of observability — the ADAPTER, not the contract. `Tracer`
-* and `Meter` are the kernel's ports, and OTel's presence stops at this subpath,
-* behind an optional peer exactly like `pino`.
-*
-* The ports are narrowings of OTel's own shapes, so what the SDK hands back
-* satisfies them with no translation in between.
-*/
-/**
-* The SDK itself, module-private: providing it is what starts it, and `release`
-* is what flushes it. It rides the graph as a RESOURCE so the kernel closes it
-* on every exit path — a span lost in `shutdown()` becomes a `teardownError` and
-* exit `2`, never silence.
-*/
 var OtelSdk = class extends Port("OtelSdk") {};
 /**
 * The OTel starter: a module providing `Tracer` and `Meter` over a `NodeSDK`
@@ -32,15 +18,32 @@ var OtelSdk = class extends Port("OtelSdk") {};
 * **Auto-instrumentation cannot live here**: the register hook must be
 * preloaded before the instrumented libraries are imported, which no DI
 * provider can promise. Preloading is the deployment's line.
+*
+* **What CAN live here is a starter's own instrumentation.** Every package
+* that contributed to `Instrumentations` is loaded and handed to the SDK, so
+* composing a starter is what declares the instrumentation and composing this
+* is what turns it on. A contribution whose optional peer is not installed
+* loads as `undefined` and is dropped — the contributor says so at `debug`,
+* since it is the one that knows why.
+*
+* The module contributes one member of its own, which loads nothing. That is
+* what makes `Instrumentations` a port the graph always has — a collector
+* depending on a set port NOTHING provides is an unmet dependency, both at
+* plan time and in `Needs`. Guice's `newSetBinder` declares the empty set for
+* the same reason.
 */
 const otel = (options) => Module("Otel")({
 	provides: [
-		Provider(OtelSdk)({
-			acquire: () => {
-				const sdk = new NodeSDK(options);
+		Provider.member(Instrumentations)({ value: () => Promise.resolve(void 0) }),
+		Provider(OtelSdk)({ offered: Instrumentations }, {
+			acquire: ({ offered }) => fromSafePromise(Promise.all(offered.map((load) => load())).then((loaded) => {
+				const sdk = new NodeSDK({
+					...options,
+					instrumentations: [...options?.instrumentations ?? [], ...loaded.filter((one) => one !== void 0)]
+				});
 				sdk.start();
-				return Ok(sdk);
-			},
+				return sdk;
+			})),
 			release: (sdk) => sdk.shutdown()
 		}),
 		Provider(Tracer)({ sdk: OtelSdk }, { sync: () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@btravstack/observability",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "Observability for @btravstack/core: a strict Logger port correlated with the kernel's units, a dependency-free JSON sink, and the lifecycle events as log lines",
   "keywords": [
     "dependency-injection",
@@ -77,19 +77,19 @@
     "typescript": "7.0.2",
     "unthrown": "5.7.0",
     "vitest": "4.1.11",
-    "@btravstack/core": "0.5.0",
-    "@btravstack/config": "0.5.0",
-    "@btravstack/di": "0.5.0",
-    "@btravstack/testing": "0.5.0"
+    "@btravstack/config": "0.7.0",
+    "@btravstack/core": "0.7.0",
+    "@btravstack/di": "0.7.0",
+    "@btravstack/testing": "0.7.0"
   },
   "peerDependencies": {
     "@opentelemetry/api": "^1.9.0",
     "@opentelemetry/sdk-node": "^0.221.0",
     "pino": "^10",
     "unthrown": "^5.0.0",
-    "@btravstack/config": "^0.5.0",
-    "@btravstack/core": "^0.5.0",
-    "@btravstack/di": "^0.5.0"
+    "@btravstack/config": "^0.7.0",
+    "@btravstack/core": "^0.7.0",
+    "@btravstack/di": "^0.7.0"
   },
   "peerDependenciesMeta": {
     "@opentelemetry/api": {