golem-enable-otlp-ts

To enable OpenTelemetry tracing for a TypeScript Golem agent, add the golem-otlp-exporter plugin to your golem.yaml and configure it with your OTLP collector endpoint. This exports telemetry data like traces, logs, and metrics directly to your monitoring stack.

The best way to export TypeScript agent metrics to an OTLP collector is using the golem-otlp-exporter plugin. It automatically exports traces, logs, and metrics without requiring an extra plugin installation, streamlining your observability pipeline across agent invocations.

Trace context propagation across Golem RPC calls works automatically by passing trace and span identifiers through inbound HTTP requests and outgoing RPC calls. This ensures end-to-end visibility for your TypeScript agent operations within your distributed tracing setup.

Yes, you can create custom spans for specific operations in a TypeScript Golem agent. Use either the golem:api/context interface or Node.js diagnostics_channel to generate custom spans, allowing you to attach useful invocation context and attributes to targeted operations.

No, you do not need an extra plugin to export logs and traces from your Golem TypeScript agent. The golem-otlp-exporter plugin automatically handles exporting telemetry to any OTLP-compatible collector once configured in your golem.yaml file.

To configure the OTLP exporter endpoint for a production Golem deployment, update your golem.yaml with the golem-otlp-exporter plugin parameters, including the specific endpoint, required signals, and headers, then run golem deploy to apply the environment settings.