Anyone tried to get Renovate bot to log to Seq? (OpenTelemetry SDK)

[Sebazzz]

I was trying to get Mend Renovate bot to log to Seq, which internally uses OpenTelemetry SDK to export traces. However, it fails:

       "err": {
         "name": "OTLPExporterError",
         "data": "\u0012\u0019Unsupported content type.",
         "code": 400,
         "message": "Bad Request",
         "stack": "OTLPExporterError: Bad Request\n    at IncomingMessage.<anonymous> (/usr/local/renovate/node_modules/.pnpm/@opentelemetry+otlp-exporter-base@0.50.0_@opentelemetry+api@1.8.0/node_modules/@opentelemetry/otlp-exporter-base/src/platform/node/util.ts:131:27)\n    at /usr/local/renovate/node_modules/.pnpm/@opentelemetry+context-async-hooks@1.23.0_@opentelemetry+api@1.8.0/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:49\n    at AsyncLocalStorage.run (node:async_hooks:346:14)\n    at AsyncLocalStorageContextManager.with (/usr/local/renovate/node_modules/.pnpm/@opentelemetry+context-async-hooks@1.23.0_@opentelemetry+api@1.8.0/node_modules/@opentelemetry/context-async-hooks/src/AsyncLocalStorageContextManager.ts:40:36)\n    at IncomingMessage.contextWrapper (/usr/local/renovate/node_modules/.pnpm/@opentelemetry+context-async-hooks@1.23.0_@opentelemetry+api@1.8.0/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:75:26)\n    at IncomingMessage.emit (node:events:530:35)\n    at IncomingMessage.emit (node:domain:488:12)\n    at endReadableNT (node:internal/streams/readable:1696:12)\n    at processTicksAndRejections (node:internal/process/task_queues:82:21)"
       }

I suppose this is some incompatibility in Seq with the OpenTelemetry SDK - is this a known issue?

Using this OTEL configuration:

OTEL_EXPORTER_OTLP_LOGS_ENDPOINT = https://my-seq-url/ingest/otlp/v1/logs
OTEL_EXPORTER_OTLP_LOGS_HEADERS = X-Seq-ApiKey=xxxxxxxx
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf

Seq is running directly on http.sys and is not proxied.

[liammclennan]

Hi @Sebazzz

In OpenTelemetry logs and traces are completely separate.

The JavaScript OpenTelemetry SDK does not support logs yet, and when sending traces it won't use the OTEL_EXPORTER_OTLP_LOGS_ENDPOINT and OTEL_EXPORTER_OTLP_LOGS_HEADERS variables.

You can use OTEL_EXPORTER_OTLP_ENDPOINT or OTEL_EXPORTER_OTLP_TRACES_ENDPOINT. Same for headers.