@atrim/instrument-node 0.5.1-1451fcf-20260105212505 → 0.5.1-21bb978-20260105202350

package/README.md

@@ -80,35 +80,6 @@ const process = Effect.gen(function* () {
 
 Available: `annotateUser`, `annotateBatch`, `annotateDataSize`, `annotateLLM`, `annotateQuery`, `annotateHttpRequest`, `annotateError`, `annotatePriority`, `annotateCache`
 
-### Effect Fiber Metadata Extraction
-
-To add Effect fiber metadata (fiber ID, status, parent span info) to your spans, you must **explicitly call** the enrichment functions:
-
-```typescript
-import { autoEnrichSpan, withAutoEnrichedSpan } from '@atrim/instrument-node/effect'
-
-// Option 1: Call autoEnrichSpan() inside a span
-const operation = Effect.gen(function* () {
-  yield* autoEnrichSpan()  // Adds fiber metadata to current span
-  // ... your logic
-}).pipe(Effect.withSpan('app.operation'))
-
-// Option 2: Use the convenience wrapper
-const operation = withAutoEnrichedSpan('app.operation')(
-  Effect.gen(function* () {
-    // ... your logic (fiber metadata added automatically)
-  })
-)
-```
-
-**Extracted metadata:**
-- `effect.fiber.id` - Unique fiber thread name
-- `effect.fiber.status` - Current fiber status
-- `effect.operation.root` / `effect.operation.nested` - Operation hierarchy
-- `effect.parent.span.id`, `effect.parent.span.name`, `effect.parent.trace.id` - Parent span info
-
-> **Note:** The `auto_extract_metadata` config option is currently not implemented. Metadata extraction requires explicit calls as shown above. See [#issue] for tracking automatic extraction support.
-
 ## Configuration (Optional)
 
 Create `instrumentation.yaml` in your project root:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atrim/instrument-node",
-  "version": "0.5.1-1451fcf-20260105212505",
+  "version": "0.5.1-21bb978-20260105202350",
   "description": "OpenTelemetry instrumentation for Node.js with centralized YAML configuration",
   "type": "module",
   "license": "MIT",

package/target/dist/index.cjs

@@ -115,6 +115,11 @@ var InstrumentationConfigSchema = zod.z.object({
     // - "standalone": Use Effect's own OTLP exporter (bypasses Node SDK filtering)
     exporter: zod.z.enum(["unified", "standalone"]).default("unified"),
     auto_extract_metadata: zod.z.boolean(),
+    // Auto-bridge OpenTelemetry context to Effect spans
+    // When true, Effect spans automatically become children of the active OTel span
+    // (e.g., HTTP request span from auto-instrumentation)
+    // This is essential for proper trace hierarchy when using Effect with HTTP frameworks
+    auto_bridge_context: zod.z.boolean().default(true),
     auto_isolation: AutoIsolationConfigSchema.optional()
   }).optional(),
   http: HttpFilteringConfigSchema.optional()
@@ -139,7 +144,8 @@ var defaultConfig = {
   effect: {
     enabled: true,
     exporter: "unified",
-    auto_extract_metadata: true
+    auto_extract_metadata: true,
+    auto_bridge_context: true
   }
 };
 function parseAndValidateConfig(content) {