@axiastudio/aioc-export-otel

Experimental OpenTelemetry Logs exporter for AIOC governance events.

This package maps GovernanceEvent records from @axiastudio/aioc-governance-events to OpenTelemetry LogRecord values and emits them through an OpenTelemetry-compatible logger.

It does not configure an OpenTelemetry SDK, processor, collector, OTLP endpoint, or delivery guarantee. Host applications remain responsible for their OpenTelemetry pipeline.

Install

npm install @axiastudio/aioc-export-otel @axiastudio/aioc-governance-events @opentelemetry/api-logs

Usage

import { logs } from "@opentelemetry/api-logs";
import { createGovernanceEventSink } from "@axiastudio/aioc-governance-events";
import { createOpenTelemetryLogExporter } from "@axiastudio/aioc-export-otel";

const logger = logs.getLogger("aioc.governance");
const exporter = createOpenTelemetryLogExporter(logger);

await run(agent, userMessage, {
  record: {
    sink: createGovernanceEventSink(exporter),
  },
});

Console Smoke

For local diagnostics, configure the OpenTelemetry SDK with ConsoleLogRecordExporter and run:

npm run export-otel:console

This prints the mapped OpenTelemetry LogRecord to stdout. It is useful for checking the adapter shape before connecting a collector or backend.

SigNoz Smoke

Start a local SigNoz stack or OpenTelemetry Collector that accepts OTLP/HTTP logs on http://localhost:4318/v1/logs, then run:

npm run export-otel:signoz

Use AIOC_OTEL_LOGS_URL to target a different collector endpoint:

AIOC_OTEL_LOGS_URL=http://localhost:4318/v1/logs npm run export-otel:signoz

In SigNoz, search logs for aioc.governance.event_id = signoz-smoke-event-1.

Status

Experimental. The adapter currently maps governance events to OpenTelemetry Logs only. Span events may be added later if a concrete use case requires them.