@themoltnet/agent-daemon 0.14.5 → 0.15.0

package/dist/main.js

@@ -1,5 +1,12 @@
 #!/usr/bin/env node
 import { createRequire } from "node:module";
+import { registerInstrumentations } from "@opentelemetry/instrumentation";
+import { DnsInstrumentation } from "@opentelemetry/instrumentation-dns";
+import { HttpInstrumentation } from "@opentelemetry/instrumentation-http";
+import { NetInstrumentation } from "@opentelemetry/instrumentation-net";
+import { PgInstrumentation } from "@opentelemetry/instrumentation-pg";
+import { PinoInstrumentation } from "@opentelemetry/instrumentation-pino";
+import { UndiciInstrumentation } from "@opentelemetry/instrumentation-undici";
 import crypto$1, { createHash } from "crypto";
 import { createHash as createHash$1 } from "node:crypto";
 import path, { dirname, isAbsolute, join, relative, resolve, sep } from "node:path";
@@ -55,6 +62,84 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 var __toCommonJS = (mod) => __hasOwnProp.call(mod, "module.exports") ? mod["module.exports"] : __copyProps(__defProp({}, "__esModule", { value: true }), mod);
 var __require = /* @__PURE__ */ createRequire(import.meta.url);
 //#endregion
+//#region ../../libs/observability/src/instrumentation.ts
+/**
+* Register OTel auto-instrumentation for common Node.js modules.
+*
+* MUST be called before any other imports that load pg, http, net, dns, or
+* pino. In ESM, place this in a dedicated side-effect module that is the
+* first import in the app entrypoint:
+*
+* ```ts
+* // instrumentation.ts (app-level)
+* import { initInstrumentation } from '@moltnet/observability';
+* initInstrumentation({ pg: true, httpIgnoreIncomingPaths: ['/health'] });
+* ```
+*
+* ```ts
+* // main.ts
+* import './instrumentation.js'; // ← MUST be first
+* import { bootstrap } from './bootstrap.js';
+* ```
+*
+* The registered instrumentations pick up the global TracerProvider once
+* it is set by `initObservability()`. Call this function first, then call
+* `initObservability()`.
+*
+* Returns the registered instrumentation instances so callers (and tests) can
+* introspect what was wired — e.g. assert that pino/undici correlation is
+* enabled. The return value is otherwise inert; callers may ignore it.
+*/
+function initInstrumentation(config) {
+	const { http = true, dns = true, net = true, pg = true, pino = true, httpIgnoreIncomingPaths = [] } = config;
+	const instrumentations = [];
+	if (http) instrumentations.push(new HttpInstrumentation({ ignoreIncomingRequestHook: httpIgnoreIncomingPaths.length > 0 ? (req) => {
+		const url = req.url ?? "";
+		return httpIgnoreIncomingPaths.some((path) => url.startsWith(path));
+	} : void 0 }), new UndiciInstrumentation());
+	if (dns) instrumentations.push(new DnsInstrumentation());
+	if (net) instrumentations.push(new NetInstrumentation());
+	if (pg) instrumentations.push(new PgInstrumentation());
+	if (pino) instrumentations.push(new PinoInstrumentation());
+	registerInstrumentations({ instrumentations });
+	return instrumentations;
+}
+//#endregion
+//#region src/instrumentation.ts
+/**
+* OTel auto-instrumentation registration for the agent daemon.
+*
+* This file MUST be imported first in main.ts — before any module that
+* transitively imports http, net, dns, undici (global fetch), or pino. In
+* ESM, imports execute in declaration order, so placing this first guarantees
+* the monkey-patches land before those modules load. In particular:
+*
+*   - UndiciInstrumentation patches `globalThis.fetch` so every outbound SDK
+*     call (@themoltnet/sdk uses global fetch — see libs/sdk/src/connect.ts)
+*     carries a W3C `traceparent` header. That is what links the daemon's
+*     trace to the rest-api server span: one distributed trace, end to end.
+*   - PinoInstrumentation injects `trace_id` / `span_id` into every pino log
+*     record, so logs correlate with the active span in Axiom. It patches
+*     pino at import time — hence the strict ordering requirement. It does
+*     NOT add a transport, so the logger's pino-pretty shutdown dance
+*     (lib/logger.ts, issue #1107) stays valid.
+*
+* The registered instrumentations bind to the global TracerProvider once it
+* is registered by `initWorkerOtel()` (lib/otel.ts, via provider.register()).
+* Registration order is fine: instrumentations created here pick up the
+* provider whenever it is set; spans only flow once it is registered.
+*
+* No `pg` instrumentation — the daemon has no direct database access. No
+* `runtime-node` — that is server-side process metrics, out of scope here.
+*/
+initInstrumentation({
+	http: true,
+	dns: true,
+	net: true,
+	pino: true,
+	pg: false
+});
+//#endregion
 //#region ../../node_modules/.pnpm/typebox@1.2.8/node_modules/typebox/build/format/date.mjs
 var DAYS = [
 	0,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@themoltnet/agent-daemon",
-  "version": "0.14.5",
+  "version": "0.15.0",
   "license": "AGPL-3.0-only",
   "type": "module",
   "description": "MoltNet agent daemon — claims and executes tasks (fulfill_brief, assess_brief) from the MoltNet task-service via Pi-headless. CLI: moltnet-agent.",
@@ -32,6 +32,12 @@
     "@earendil-works/pi-coding-agent": "^0.74.0",
     "@opentelemetry/api": "^1.9.0",
     "@opentelemetry/exporter-trace-otlp-proto": "^0.212.0",
+    "@opentelemetry/instrumentation": "^0.212.0",
+    "@opentelemetry/instrumentation-dns": "^0.55.0",
+    "@opentelemetry/instrumentation-http": "^0.212.0",
+    "@opentelemetry/instrumentation-net": "^0.56.0",
+    "@opentelemetry/instrumentation-pino": "^0.58.0",
+    "@opentelemetry/instrumentation-undici": "^0.22.0",
     "@opentelemetry/resources": "^2.5.1",
     "@opentelemetry/sdk-trace-base": "^2.5.1",
     "@opentelemetry/sdk-trace-node": "^2.5.1",
@@ -39,9 +45,9 @@
     "pino": "^10.3.1",
     "pino-pretty": "^13.1.3",
     "@themoltnet/agent-daemon-state": "0.2.0",
-    "@themoltnet/pi-extension": "0.22.4",
     "@themoltnet/agent-runtime": "0.22.4",
-    "@themoltnet/sdk": "0.106.0"
+    "@themoltnet/sdk": "0.106.0",
+    "@themoltnet/pi-extension": "0.22.5"
   },
   "devDependencies": {
     "tsx": "^4.7.0",
@@ -50,7 +56,8 @@
     "vitest": "^3.0.0",
     "@moltnet/bootstrap": "0.1.0",
     "@moltnet/crypto-service": "0.1.0",
-    "@moltnet/tasks": "0.1.0"
+    "@moltnet/tasks": "0.1.0",
+    "@moltnet/observability": "0.1.0"
   },
   "nx": {
     "tags": [