@deepseek-ai/dsh-session-telemetry-otel 0.1.7-rc.2 → 0.2.0-rc.2

package/README.i18n.yaml

@@ -9,8 +9,8 @@
   en: f8ea869792c8b207
   zh: bc076172ce22ba9b
 /deepseek-ai-dsh-session-telemetry-otel/summary:
-  en: 1c5d2f15cb13e318
-  zh: 5e061a16cd38c4c5
+  en: 828903209ef34983
+  zh: 8eac63f1e8df15d8
 /deepseek-ai-dsh-session-telemetry-otel/table-of-contents:
   en: d152484eb41ac6b4
   zh: 09388d293f9be9cb
@@ -21,29 +21,29 @@
   en: bc7e598148a7f8c3
   zh: 0209c6aa258ec134
 /deepseek-ai-dsh-session-telemetry-otel/use-this-package/minimal-configuration:
-  en: 3de0d5db3156a7e4
-  zh: 71199133cd9998c4
+  en: 11845fd50dc0a494
+  zh: ee990bfca3621bd3
 /deepseek-ai-dsh-session-telemetry-otel/use-this-package/what-leaves-the-machine:
-  en: b94ca8299ad60c5d
-  zh: 3791131f3440e3b3
+  en: 2a5ddd227e400455
+  zh: 74b7bd9b9161b054
 /deepseek-ai-dsh-session-telemetry-otel/use-this-package/failures-and-shutdown:
-  en: 20c6e78df8ad2c2a
-  zh: fd6a00f98c4cc05c
+  en: a66831cb9de57e04
+  zh: 3ada28bb868e0932
 /deepseek-ai-dsh-session-telemetry-otel/understand-the-implementation:
   en: ee672a6a6f0fa02d
   zh: c3bab8e6b60e768c
 /deepseek-ai-dsh-session-telemetry-otel/understand-the-implementation/design-concept:
-  en: d5e1f8249d3eea34
-  zh: 7a6915e33390f4ae
+  en: 34f8a88224a1f6cf
+  zh: 40839dabaea39602
 /deepseek-ai-dsh-session-telemetry-otel/understand-the-implementation/source-map:
   en: 0b99d2e5c27213cd
   zh: 3cbdaa7f6a45d81a
 /deepseek-ai-dsh-session-telemetry-otel/understand-the-implementation/capture-wiring:
-  en: 9bdc01d0fa130b3a
-  zh: 63bf30c4cc983ca0
+  en: 5c85eb0992eb5b2b
+  zh: a19cdd5814c0e2b9
 /deepseek-ai-dsh-session-telemetry-otel/understand-the-implementation/field-mapping:
-  en: 38590f3afee40bb8
-  zh: b2fc1f4341008d79
+  en: a42e9e081fb93bee
+  zh: b8e817c2455278b9
 /deepseek-ai-dsh-session-telemetry-otel/further-exploration:
   en: 155b75490ec65d86
   zh: 07d37d6e4ac90c89
@@ -57,5 +57,5 @@
   en: e43087aea7af4c9e
   zh: f8b529e2012b4c63
 /deepseek-ai-dsh-session-telemetry-otel/known-limitations-and-deferred-work/dev-note:
-  en: a770daec456212ab
-  zh: 1b861566d591837d
+  en: 0065df2648b09ac9
+  zh: b5bac41fc3aec70e

package/README.md

@@ -9,7 +9,9 @@ English | [中文](README.zh.md)
 
 ## Summary
 
-`dsh-session-telemetry-otel` exports session records through the OTel JS SDK only after new explicit feedback, for all users and providers, including `deepseek-official`. `FEEDBACK_ONLY` releases the canonical prefix through that feedback, including context; later records wait for the next explicit feedback. `DISABLED` constructs no transport. SDK batching can finish an authorized upload without another user interaction or model call. Deployments own their redaction rules.
+The adapter injects `otel`; the [shared OTel plugin](../../telemetry/otel/README.md) creates its independent Session-log channel. Authorization, redaction, identity, scope version, configuration, and the shutdown deadline remain owned here.
+
+`dsh-session-telemetry-otel` exports session records through the OTel JS SDK only after new explicit feedback, for all users and providers, including `deepseek-official`. `FEEDBACK_ONLY` releases the canonical prefix through that feedback, including context; later records wait for the next explicit feedback. `DISABLED` constructs no transport. Scheduled batching can finish an authorized upload without another user interaction or model call. Deployments own their redaction rules.
 
 ## Table of Contents
 
@@ -38,7 +40,7 @@ Programmatic TypeScript configuration uses the exported `SessionTelemetryMode` e
 
 ### Minimal configuration
 
-Uploading modes require an exporter URL and accept the SDK option blocks verbatim:
+Uploading modes require an exporter URL. Processor settings control the independent Session-log queue; routing headers are explicit `exporter.headers` values.
 
 ```yaml
 - id: sessionTelemetry-otel
@@ -46,31 +48,34 @@ Uploading modes require an exporter URL and accept the SDK option blocks verbati
   config:
     mode: FEEDBACK_ONLY       # optional; defaults to FEEDBACK_ONLY
     shutdownTimeoutMillis: 3000 # optional; defaults to 3000
-    exporter:                # passed verbatim to the SDK's OTLP/HTTP log exporter
+    exporter:                # explicit SDK transport settings
       url: https://collector.example.com/v1/logs
       headers:
         authorization: !!js `Bearer ${process.env.OTLP_TOKEN}`
-    processor: {}            # optional; passed verbatim to BatchLogRecordProcessor
+    processor: {}            # optional; byte/count batching and per-request watchdog
 ```
 
 | Field | Default | Meaning |
 |---|---|---|
 | `mode` | `FEEDBACK_ONLY` | Sharing policy: `FEEDBACK_ONLY` or `DISABLED` |
 | `exporter.url` | required in uploading modes | Full OTLP logs endpoint; must parse as `http(s)` |
-| `exporter`, `processor` | — | Passed verbatim to the SDK exporter and batch processor |
-| `shutdownTimeoutMillis` | `3,000` | Outer deadline for the SDK's complete shutdown sequence |
+| `exporter`, `processor` | — | SDK transport plus byte/count batching; headers/TLS identity are not inherited from the environment. Agent factories own their returned agent settings, including keepAlive |
+| `shutdownTimeoutMillis` | `3,000` | Outer deadline for all queued HTTP requests; remaining queued sends stop at expiry |
+| `maxRequestBytes` | `4,000,000` | Maximum complete OTLP JSON request bytes before gzip; may only be lowered |
 
 Direct `ctx.sessionTelemetry.emit()` calls are no-ops in every mode and cannot bypass feedback authorization. Inherited parent feedback does not authorize a child export: the child needs new feedback of its own. Its authorized prefix then includes inherited context.
 
-Model requests, request headers, Session creation or adoption, restoration, and plugin mount or HMR do not authorize capture. Stored feedback alone triggers nothing. SDK scheduled flush and shutdown may finish batches authorized earlier, but never capture new records.
+Model requests, request headers, Session creation or adoption, restoration, and plugin mount or HMR do not authorize capture. Stored feedback alone triggers nothing. Scheduled flush and shutdown may finish batches authorized earlier, but never capture new records.
 
 ### What leaves the machine
 
-In uploading modes, records carry the complete `event.data` as the seam's `sessionTelemetry/record` waterfall returns it — message content, tool arguments and results, the system prompt and tool schemas, todo text, compaction summaries, feedback text, and the session `cwd`. Provider credentials never appear: adapter API keys are constructor parameters, not session events, so they are structurally absent from the log and therefore from telemetry. `DISABLED` constructs no SDK pipeline and hands no capture to a backend.
+Each Session event becomes one `eventName: "session-log"` record. `attributes.sessionId` is the collector Session identity; `attributes.content` encodes the complete event envelope with redacted `event.data`. JSON values are preserved, not the original JSONL bytes or key ordering. Legacy `session.id`, `event.seq`, and `event.type` metadata remain for existing consumers. Resources carry application and anonymous-user identity; scope carries the backend package name and version. The base profile uses `https://dsh-otel-collector.deepseeksvc.com/v1/logs`; `DSH_TELEMETRY_OTLP_URL` overrides it. No channel header is added implicitly.
+
+The shared OTel channel measures each record once with the SDK OTLP JSON serializer, including its resource/scope envelope, then greedily packs requests using those conservative sizes. A single oversized event produces one rejection diagnostic without truncation. Session logs never mix with product analytics in a request. Capture handoff and shutdown are not collector acknowledgements.
 
 ### Failures and shutdown
 
-Misconfiguration fails at plugin load: a missing or non-`http(s)` `exporter.url`, a non-positive-integer `processor.maxExportBatchSize` (which the SDK accepts but then hangs on at shutdown), and an invalid `shutdownTimeoutMillis` all reject before any record is exported. During shutdown, OTel awaits `exporter.forceFlush()` before the processor's bounded completion promise; if that transport promise never settles, this package abandons the wait at `shutdownTimeoutMillis`, logs the contained failure, and lets application teardown continue — records still pending then may be lost at process exit.
+Invalid byte limits, non-positive queue/timer values, `maxExportBatchSize > maxQueueSize`, invalid endpoints, and invalid shutdown deadlines fail at load. Processor defaults are 2,048 queued records, 512 records per request, a 1,000 ms scheduling delay, and a 30,000 ms request watchdog. Byte limits may split a count batch into multiple serial HTTP requests. Each request waits for SDK export-queue cleanup after its callback before the next starts. `exportTimeoutMillis` warns per request but never frees an unsettled transport slot; the SDK transport owns network timeout/retry. Shutdown drains these requests until `shutdownTimeoutMillis`; expiry discards the remaining queue and prevents further sends, while an active request may still settle. Large prefixes can therefore remain partially unsent at CLI exit.
 
 -----
 
@@ -84,7 +89,7 @@ This section explains the backend's composition; the observable behavior is full
 
 ### Design concept
 
-The backend is a thin adapter over the OTel JS SDK: it owns feedback authorization, resource identity, and an outer shutdown deadline. Canonical ledger records use the `@deepseek-ai/dsh-session-telemetry-otel` instrumentation scope; this backend captures no operational records. Resource identity carries `service.name`/`service.version` from `dsh-llm`'s `APP_IDENTITY` plus the anonymous `user.id` (from `$DSH_HOME/.anonymous-user-id`), once per export batch rather than per record.
+The backend owns feedback authorization, identity, and shutdown. The shared OTel service owns channel creation, byte/count scheduling, record construction, JSON transport, compression, and retries. Resource identity carries `service.name`/`service.version` from `APP_IDENTITY` and anonymous `user.id`; the scope retains this package’s name and version.
 
 ### Source map
 
@@ -94,11 +99,11 @@ The backend is a thin adapter over the OTel JS SDK: it owns feedback authorizati
 
 ### Capture wiring
 
-The backend uses on-demand capture with stored history included. Only new own `feedback/record`, `feedback/message-put`, or `feedback/message-delete` events trigger live capture, bounded by that event. A cold `feedback/committed` notification supplies its committed canonical snapshot without publishing a live Session or Agent. Same-object handoff cursors suppress repeated capture. The backend implements no `flush()`; the SDK owns batching and shutdown drain.
+The backend captures history on demand through new own feedback events or committed cold snapshots. Its private reporter serializes queued HTTP requests even after a watchdog fires; an outer shutdown deadline stops the remaining queue. It exposes no extra flush entry point.
 
 ### Field mapping
 
-Each telemetry record maps to one SDK log record with captured timestamp, severity, body, and attributes. Feedback authorizes the complete unhanded prefix, not only the feedback payload.
+Each capture record supplies a separately copied event envelope and redacted payload to `SessionLogReporter`; serialization retains optional surface metadata and the event sequence/time. Feedback authorizes the complete unhanded prefix, not only the feedback payload.
 
 </details>
 
@@ -148,4 +153,4 @@ None.
 
 </details>
 
-**Runtime invariant:** No companion is published. Mode selection changes capture handoff, SDK setup, and local diagnostics without mutating session or service state an independent companion can compare. Export remains inside the SDK past the backend boundary.
+**Runtime invariant:** No companion is published. Mode selection changes capture handoff, SDK setup, and local diagnostics without mutating session or service state an independent companion can compare. Collector delivery cannot be inferred from local queue state.

package/README.zh.md

@@ -9,7 +9,9 @@ kind: "package-reference"
 
 ## 概述
 
-`dsh-session-telemetry-otel` 仅在新的显式反馈后通过 OTel JS SDK 导出会话记录，适用于所有用户和提供方，包括 `deepseek-official`。`FEEDBACK_ONLY` 释放截至该反馈的权威日志前缀，包含上下文；后续记录等待下一次显式反馈。`DISABLED` 不构造传输。SDK 批处理可完成已授权的上传，无需另一次用户交互或模型调用。部署方负责脱敏规则。
+适配器注入 `otel`；[共享 OTel 插件](../../telemetry/otel/README.zh.md) 创建其独立 Session 日志通道。授权、脱敏、身份、scope 版本、配置和关闭期限仍由本包负责。
+
+`dsh-session-telemetry-otel` 仅在新的显式反馈后通过 OTel JS SDK 导出会话记录，适用于所有用户和提供方，包括 `deepseek-official`。`FEEDBACK_ONLY` 释放截至该反馈的权威日志前缀，包含上下文；后续记录等待下一次显式反馈。`DISABLED` 不构造传输。定时批处理可完成已授权的上传，无需另一次用户交互或模型调用。部署方负责脱敏规则。
 
 ## 目录
 
@@ -38,7 +40,7 @@ kind: "package-reference"
 
 ### 最小配置
 
-上传模式需要导出器 URL，并原样接受 SDK 选项块：
+启用上传的模式必须提供 exporter URL。processor 设置控制独立的 Session 日志队列；路由头通过 `exporter.headers` 显式配置。
 
 ```yaml
 - id: sessionTelemetry-otel
@@ -46,31 +48,34 @@ kind: "package-reference"
   config:
     mode: FEEDBACK_ONLY       # optional; defaults to FEEDBACK_ONLY
     shutdownTimeoutMillis: 3000 # optional; defaults to 3000
-    exporter:                # passed verbatim to the SDK's OTLP/HTTP log exporter
+    exporter:                # explicit SDK transport settings
       url: https://collector.example.com/v1/logs
       headers:
         authorization: !!js `Bearer ${process.env.OTLP_TOKEN}`
-    processor: {}            # optional; passed verbatim to BatchLogRecordProcessor
+    processor: {}            # optional; byte/count batching and per-request watchdog
 ```
 
 | 字段 | 默认值 | 含义 |
 |---|---|---|
 | `mode` | `FEEDBACK_ONLY` | 共享策略：`FEEDBACK_ONLY` 或 `DISABLED` |
 | `exporter.url` | 上传模式必填 | 完整 OTLP 日志端点；必须能解析为 `http(s)` |
-| `exporter`、`processor` | — | 原样传给 SDK 导出器与批处理器 |
-| `shutdownTimeoutMillis` | `3,000` | SDK 完整关闭序列的外层截止时间 |
+| `exporter`, `processor` | — | SDK 传输及字节/条数聚合；不继承环境中的头部和 TLS 身份。agent 工厂负责返回实例的设置，包括 keepAlive |
+| `shutdownTimeoutMillis` | `3,000` | 所有排队 HTTP 请求的外层期限；到期后停止剩余排队发送 |
+| `maxRequestBytes` | `4,000,000` | gzip 前完整 OTLP JSON 请求的最大字节数；只能调低 |
 
 直接调用 `ctx.sessionTelemetry.emit()` 在任何模式下都是空操作，不能绕过反馈授权。继承的父会话反馈不授权子会话导出：子会话需要新的自身反馈。授权后的前缀包含继承的上下文。
 
-模型请求、请求头、Session 创建或接纳、恢复，以及插件挂载或 HMR（热模块替换）均不授权捕获。仅凭已存储的反馈不会触发任何操作。SDK 定时刷新和关闭可以完成先前已授权的批次，但绝不捕获新记录。
+模型请求、请求头、Session 创建或接纳、恢复，以及插件挂载或 HMR（热模块替换）均不授权捕获。仅凭已存储的反馈不会触发任何操作。定时刷新和关闭可以完成先前已授权的批次，但绝不捕获新记录。
 
 ### 哪些数据会离开本机
 
-在上传模式中，记录携带 seam 的 `sessionTelemetry/record` waterfall（瀑布式事件）返回的完整 `event.data`——消息内容、工具参数与结果、系统提示词与工具 schema、todo 文本、压缩（compaction）摘要、反馈文本，以及会话 `cwd`。提供方凭据绝不会出现：适配器的 API key 是构造函数参数而非会话事件，因此它们在结构上就不存在于日志中，也就不存在于遥测中。`DISABLED` 不构造 SDK 流水线，也不把任何捕获内容交给后端。
+每条 Session 事件对应一个 `eventName: "session-log"` 记录。`attributes.sessionId` 是 collector 使用的 Session 身份；`attributes.content` 编码完整事件 envelope 和脱敏后的 `event.data`。保留的是 JSON 值，不保证原 JSONL 字节或键顺序相同。为现有消费者保留 `session.id`、`event.seq` 和 `event.type` 元数据。Resource 携带应用和匿名用户身份；scope 携带后端包名和版本。基础配置使用 `https://dsh-otel-collector.deepseeksvc.com/v1/logs`，可用 `DSH_TELEMETRY_OTLP_URL` 覆盖。不隐式添加 channel 头。
+
+共享 OTel 通道使用 SDK 的 OTLP JSON 序列化器对每条记录计量一次，包含其 resource/scope envelope，再按保守大小顺序组包。单条超限事件产生一次拒绝诊断且不截断。Session 日志不会与产品埋点混在一个请求中。捕获交接和关闭完成不代表 collector 确认。
 
 ### 失败与关闭
 
-配置错误会在插件加载时失败：缺少或非 `http(s)` 的 `exporter.url`、非正整数的 `processor.maxExportBatchSize`（SDK 会接受该值，随后却在关闭时挂起）以及无效的 `shutdownTimeoutMillis` 都会在任何记录导出前被拒绝。关闭期间，OTel 会先等待 `exporter.forceFlush()`，再等待处理器有界完成 promise；如果该传输 promise 始终不结算，本包会在 `shutdownTimeoutMillis` 到期时放弃等待、记录已隔离的失败，并让应用继续拆卸——届时仍待处理的记录可能在进程退出时丢失。
+无效字节上限、非正队列/计时值、`maxExportBatchSize > maxQueueSize`、无效 endpoint 或关闭期限在加载时失败。processor 默认队列为 2,048 条、单请求最多 512 条、调度延迟 1,000 ms、请求监测期限 30,000 ms。字节上限可能将按条数划分的批次拆成多个串行 HTTP 请求。每个请求在回调后等待 SDK 导出队列清理完成，才启动下一个请求。`exportTimeoutMillis` 针对每个请求告警，但不会释放未结束的传输槽位；SDK transport 负责网络超时和重试。关闭时发送这些请求直到 `shutdownTimeoutMillis`，到期后丢弃剩余队列并禁止后续发送，在途请求仍可能结束。因此较大的授权前缀在 CLI 退出时可能只发送了一部分。
 
 -----
 
@@ -84,7 +89,7 @@ kind: "package-reference"
 
 ### 设计理念
 
-后端是对 OTel JS SDK 的薄适配层：它拥有反馈授权、资源身份与外层关闭截止时间。权威 ledger 记录使用 `@deepseek-ai/dsh-session-telemetry-otel` 插桩作用域；此后端不捕获运维记录。资源身份携带 `service.name`/`service.version`（来自 `dsh-llm` 的 `APP_IDENTITY`）以及匿名 `user.id`（来自 `$DSH_HOME/.anonymous-user-id`），按导出批次携带一次，而非逐条记录。
+后端负责反馈授权、身份和关闭。共享 OTel 服务负责通道创建、字节和条数调度、记录构造、JSON 传输、压缩与重试。Resource 身份携带 `APP_IDENTITY` 中的 `service.name` / `service.version` 以及匿名 `user.id`；scope 保留本包的名称和版本。
 
 ### 源码地图
 
@@ -94,11 +99,11 @@ kind: "package-reference"
 
 ### 捕获接线
 
-后端使用包含存储历史的按需捕获。只有新的自身 `feedback/record`、`feedback/message-put` 或 `feedback/message-delete` 事件触发活跃会话捕获，并以该事件为上限。冷会话 `feedback/committed` 通知提供已提交的权威快照，不发布存活 Session 或 Agent。同对象交接游标抑制重复捕获。后端不实现 `flush()`；SDK 负责批处理和关闭排空。
+后端按需捕获历史，由新的自身反馈事件或已提交的冷会话快照触发。私有 reporter 串行发送排队 HTTP 请求，即使监测期限已触发也不会重叠；外层关闭期限停止剩余队列。不额外暴露 flush 入口。
 
 ### 字段映射
 
-每条遥测记录映射为一条 SDK 日志记录，携带捕获的时间戳、严重级别、正文和属性。反馈授权的是尚未交接的完整前缀，而非只有反馈载荷。
+每条采集记录向 `SessionLogReporter` 提供单独复制的事件信封和脱敏后的载荷；序列化保留可选的呈现元数据及事件序号和时间。反馈授权整个尚未交接的前缀，而不只是反馈载荷。
 
 </details>
 
@@ -148,4 +153,4 @@ kind: "package-reference"
 
 </details>
 
-**运行时不变式：** 不发布伴生入口。模式选择只改变 capture handoff、SDK setup 与本地 diagnostics，不改变可由独立 companion 对照的会话或服务状态。导出在越过后端边界后仍由 SDK 内部处理。
+**运行时不变式：** 不发布伴生入口。模式选择只改变 capture handoff、SDK setup 与本地 diagnostics，不改变可由独立 companion 对照的会话或服务状态。无法根据本地队列状态推断 collector 是否收到记录。

package/lib/index.js

@@ -4,25 +4,17 @@ import { Session } from "@deepseek-ai/dsh-session";
 import { SessionTelemetryBackend, SessionTelemetryCoordinator } from "@deepseek-ai/dsh-session-telemetry";
 import { APP_IDENTITY } from "@deepseek-ai/dsh-llm";
 import { getOrCreateAnonymousUserId } from "@deepseek-ai/dsh-anonymous-user-id";
-import { BatchLogRecordProcessor, LoggerProvider } from "@opentelemetry/sdk-logs";
-import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
 import { SeverityNumber } from "@opentelemetry/api-logs";
-import { resourceFromAttributes } from "@opentelemetry/resources";
 //#region lib/types/index.js
 /**
 * OpenTelemetry Service Provider for the DeepSeek Harness telemetry capability.
 *
-* Composes the OTel JS SDK as-is — a `LoggerProvider` with a
-* `BatchLogRecordProcessor` and an OTLP/HTTP log exporter — and maps each
-* record handed over by the capture coordinator onto `logger.emit()`. After that call,
-* batching, retry, queueing, and loss policy use the SDK's documented behavior, configured
-* verbatim through the `exporter`/`processor` passthroughs. This package owns
-* capture mode and an outer shutdown deadline: the SDK's export timeout does
-* not bound its preceding `forceFlush()` wait.
+* Authorizes feedback-bounded capture and hands complete event strings to the
+* Session-log reporter. This plugin owns resource identity and an outer
+* shutdown deadline; the reporter owns byte-bounded SDK delivery.
 *
 * @module @deepseek-ai/dsh-session-telemetry-otel
 */
-const { version } = createRequire(import.meta.url)("../package.json");
 /** Session-sharing policy selected by {@link Config.mode}. */
 var SessionTelemetryMode;
 (function(SessionTelemetryMode) {
@@ -67,34 +59,25 @@ function sharingStatusFor(mode) {
 }
 /**
 * Schemastery validator for {@link Config}; cordis runs it before the plugin
-* starts. It checks only the top-level fields; value checks live in the constructor
-* so their errors name the fields. Both SDK option objects pass through unchanged:
-* the SDK defines and validates their fields. Re-declaring them here would
-* silently drop every field this plugin did not repeat.
+* starts. The constructor validates endpoint and shutdown requirements; the
+* reporter validates Session byte and queue limits. SDK transport and
+* processor settings retain their upstream types.
 */
 const Config = z.object({
 	mode: z.union(Object.values(SessionTelemetryMode)).default(DEFAULT_TELEMETRY_MODE),
 	exporter: z.any(),
 	processor: z.any(),
-	shutdownTimeoutMillis: z.number()
+	shutdownTimeoutMillis: z.number(),
+	maxRequestBytes: z.number().step(1).min(1).max(4e6)
 });
 /** Default outer allowance for the SDK's complete shutdown sequence. */
 const DEFAULT_SHUTDOWN_TIMEOUT_MILLIS = 3e3;
 const MAX_TIMER_DELAY_MILLIS = 2147483647;
 /** Severity mapping from the Service Definition's three-level vocabulary to OTel severity numbers. */
 const SEVERITY = {
-	info: {
-		severityNumber: SeverityNumber.INFO,
-		severityText: "INFO"
-	},
-	warn: {
-		severityNumber: SeverityNumber.WARN,
-		severityText: "WARN"
-	},
-	error: {
-		severityNumber: SeverityNumber.ERROR,
-		severityText: "ERROR"
-	}
+	info: SeverityNumber.INFO,
+	warn: SeverityNumber.WARN,
+	error: SeverityNumber.ERROR
 };
 /**
 * The backend plugin — the only entry a deployment loads. It always registers
@@ -103,7 +86,7 @@ const SEVERITY = {
 * SDK state and listens only to warn when recorded feedback stays local.
 */
 var OpenTelemetrySessionBackend = class extends SessionTelemetryBackend {
-	static inject = ["sessions"];
+	static inject = ["sessions", "otel"];
 	static Config = Config;
 	provider;
 	shutdownTimeoutMillis;
@@ -134,24 +117,40 @@ var OpenTelemetrySessionBackend = class extends SessionTelemetryBackend {
 		const shutdownTimeoutMillis = config.shutdownTimeoutMillis ?? 3e3;
 		if (!Number.isFinite(shutdownTimeoutMillis) || shutdownTimeoutMillis <= 0 || shutdownTimeoutMillis > MAX_TIMER_DELAY_MILLIS) throw new Error(`session-telemetry-otel: shutdownTimeoutMillis must be a positive finite number no greater than ${MAX_TIMER_DELAY_MILLIS}, got ${String(shutdownTimeoutMillis)}`);
 		this.shutdownTimeoutMillis = shutdownTimeoutMillis;
-		this.provider = new LoggerProvider({
-			resource: resourceFromAttributes({
+		const { version } = createRequire(import.meta.url)("../package.json");
+		const reporter = ctx.otel.createSessionLogReporter({
+			scope: {
+				name: "@deepseek-ai/dsh-session-telemetry-otel",
+				version
+			},
+			exporter: {
+				...config.exporter,
+				url
+			},
+			...config.processor === void 0 ? {} : { processor: config.processor },
+			...config.maxRequestBytes === void 0 ? {} : { maxRequestBytes: config.maxRequestBytes },
+			resourceAttributes: {
 				"service.name": APP_IDENTITY.product,
 				"service.version": APP_IDENTITY.version,
 				"user.id": getOrCreateAnonymousUserId()
-			}),
-			processors: [new BatchLogRecordProcessor({
-				...config.processor,
-				exporter: new OTLPLogExporter(config.exporter)
-			})]
+			},
+			onFailure: (message, error) => {
+				ctx.logger.warn(message, error);
+			}
 		});
-		const ledger = this.provider.getLogger("@deepseek-ai/dsh-session-telemetry-otel", version);
+		this.provider = reporter;
 		const enqueue = (record) => {
-			ledger.emit({
-				timestamp: record.time,
-				observedTimestamp: record.time,
-				...SEVERITY[record.severity],
-				body: record.body,
+			if (record.sourceEvent === void 0) {
+				ctx.logger.warn("Session log record withheld: redaction removed sourceEvent");
+				return;
+			}
+			reporter.reportSessionLog({
+				sessionId: record.sourceEvent.sessionId,
+				event: {
+					...record.sourceEvent.envelope,
+					data: record.body
+				},
+				severityNumber: SEVERITY[record.severity],
 				attributes: record.attributes
 			});
 		};
@@ -185,13 +184,10 @@ var OpenTelemetrySessionBackend = class extends SessionTelemetryBackend {
 	*/
 	emit(_record) {}
 	/**
-	* Ask the SDK to drain and quiesce, but reject after the backend-owned
-	* deadline. OTel's processor export timeout wraps `exportCompleted` only;
-	* shutdown awaits `exporter.forceFlush()` first, which can remain pending
-	* when the transport never obtains a socket. The provider promise remains
-	* observed after the deadline so a later rejection cannot become unhandled.
-	* `DISABLED` has no provider and resolves immediately.
-	* @returns resolves when the SDK pipeline quiesces or is disabled, or rejects at the configured deadline.
+	* Drain queued HTTP requests until the deployment deadline. The watchdog
+	* never releases an unsettled transport slot. At the outer deadline,
+	* queued records are abandoned and no further requests may start.
+	* @returns completion after transport shutdown, or rejection at the configured deadline.
 	*/
 	async shutdown() {
 		if (this.provider === void 0) return;
@@ -199,6 +195,7 @@ var OpenTelemetrySessionBackend = class extends SessionTelemetryBackend {
 		let timer;
 		const deadline = new Promise((_resolve, reject) => {
 			timer = setTimeout(() => {
+				this.provider?.stopPending();
 				reject(/* @__PURE__ */ new Error(`session-telemetry-otel: provider shutdown exceeded ${this.shutdownTimeoutMillis}ms`));
 			}, this.shutdownTimeoutMillis);
 		});

package/lib/types/index.d.ts

@@ -1,20 +1,16 @@
 /**
  * OpenTelemetry Service Provider for the DeepSeek Harness telemetry capability.
  *
- * Composes the OTel JS SDK as-is — a `LoggerProvider` with a
- * `BatchLogRecordProcessor` and an OTLP/HTTP log exporter — and maps each
- * record handed over by the capture coordinator onto `logger.emit()`. After that call,
- * batching, retry, queueing, and loss policy use the SDK's documented behavior, configured
- * verbatim through the `exporter`/`processor` passthroughs. This package owns
- * capture mode and an outer shutdown deadline: the SDK's export timeout does
- * not bound its preceding `forceFlush()` wait.
+ * Authorizes feedback-bounded capture and hands complete event strings to the
+ * Session-log reporter. This plugin owns resource identity and an outer
+ * shutdown deadline; the reporter owns byte-bounded SDK delivery.
  *
  * @module @deepseek-ai/dsh-session-telemetry-otel
  */
 import z from '@deepseek-ai/schemastery';
 import type { Context } from '@deepseek-ai/cordis';
 import { SessionTelemetryBackend, type SessionTelemetryRecord, type SessionTelemetrySharingStatus } from '@deepseek-ai/dsh-session-telemetry';
-import { type BatchLogRecordProcessorOptions } from '@opentelemetry/sdk-logs';
+import type { BatchLogRecordProcessorOptions } from '@opentelemetry/sdk-logs';
 import type { OTLPExporterNodeConfigBase } from '@opentelemetry/otlp-exporter-base';
 /** Session-sharing policy selected by {@link Config.mode}. */
 export declare enum SessionTelemetryMode {
@@ -24,37 +20,36 @@ export declare enum SessionTelemetryMode {
 /** Default session-sharing policy for schema and direct construction. */
 export declare const DEFAULT_TELEMETRY_MODE = SessionTelemetryMode.FEEDBACK_ONLY;
 /**
- * Plugin configuration: one sharing policy, two verbatim SDK option objects,
- * and one DSH-owned shutdown bound. Uploading modes validate their endpoint
+ * Plugin configuration: sharing policy, SDK transport options, byte/count queue
+ * settings, and an overall shutdown bound. Uploading modes validate their endpoint
  * and shutdown deadline at plugin load; `DISABLED` reads neither.
  */
 export interface Config {
     /** Defaults to `FEEDBACK_ONLY`: capture session history only when feedback is explicitly submitted. */
     mode?: SessionTelemetryMode;
     /**
-     * Passed verbatim to the SDK's OTLP/HTTP log exporter — the complete
-     * `OTLPExporterNodeConfigBase` shape (`headers`, `timeoutMillis`,
-     * `compression`, `keepAlive`, …), owned and documented by the SDK. `url`
-     * is the one field this package requires and validates itself.
+     * Explicit SDK HTTP transport settings, including optional routing headers.
+     * Ambient credentials are not inherited. URL is required while uploading.
      */
     exporter?: OTLPExporterNodeConfigBase & {
         /** Full logs endpoint (e.g. `https://collector.example.com/v1/logs`). Required outside `DISABLED`; validated at load. */
         url?: string;
     };
     /**
-     * Passed verbatim to `BatchLogRecordProcessor` (minus the exporter slot,
-     * which this plugin fills); the SDK owns and documents these knobs.
+     * Count, queue, cadence, and per-request watchdog settings for the byte-bounded
+     * processor. A watchdog warning never releases an unsettled transport slot.
      */
     processor?: Omit<BatchLogRecordProcessorOptions, 'exporter'>;
     /** Maximum time spent awaiting the SDK provider's complete shutdown path. */
     shutdownTimeoutMillis?: number;
+    /** Uncompressed OTLP request byte limit, at most 4,000,000. */
+    maxRequestBytes?: number;
 }
 /**
  * Schemastery validator for {@link Config}; cordis runs it before the plugin
- * starts. It checks only the top-level fields; value checks live in the constructor
- * so their errors name the fields. Both SDK option objects pass through unchanged:
- * the SDK defines and validates their fields. Re-declaring them here would
- * silently drop every field this plugin did not repeat.
+ * starts. The constructor validates endpoint and shutdown requirements; the
+ * reporter validates Session byte and queue limits. SDK transport and
+ * processor settings retain their upstream types.
  */
 export declare const Config: z<Config>;
 /** Default outer allowance for the SDK's complete shutdown sequence. */
@@ -79,13 +74,10 @@ export declare class OpenTelemetrySessionBackend extends SessionTelemetryBackend
      */
     emit(_record: SessionTelemetryRecord): void;
     /**
-     * Ask the SDK to drain and quiesce, but reject after the backend-owned
-     * deadline. OTel's processor export timeout wraps `exportCompleted` only;
-     * shutdown awaits `exporter.forceFlush()` first, which can remain pending
-     * when the transport never obtains a socket. The provider promise remains
-     * observed after the deadline so a later rejection cannot become unhandled.
-     * `DISABLED` has no provider and resolves immediately.
-     * @returns resolves when the SDK pipeline quiesces or is disabled, or rejects at the configured deadline.
+     * Drain queued HTTP requests until the deployment deadline. The watchdog
+     * never releases an unsettled transport slot. At the outer deadline,
+     * queued records are abandoned and no further requests may start.
+     * @returns completion after transport shutdown, or rejection at the configured deadline.
      */
     shutdown(): Promise<void>;
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@deepseek-ai/dsh-session-telemetry-otel",
-  "description": "OpenTelemetry backend for the DeepSeek Harness telemetry seam: hands captured session records to the OTel JS SDK's log pipeline",
-  "version": "0.1.7-rc.2",
+  "description": "Feedback-authorized Session logs over byte-bounded OpenTelemetry HTTP requests",
+  "version": "0.2.0-rc.2",
   "publishConfig": {
     "access": "public"
   },
@@ -27,39 +27,38 @@
   ],
   "license": "MIT",
   "dependencies": {
-    "@opentelemetry/api": "^1.9.1",
     "@opentelemetry/api-logs": "^0.220.0",
-    "@opentelemetry/exporter-logs-otlp-http": "^0.220.0",
     "@opentelemetry/otlp-exporter-base": "^0.220.0",
-    "@opentelemetry/resources": "^2.9.0",
     "@opentelemetry/sdk-logs": "^0.220.0",
     "@deepseek-ai/schemastery": "~3.18.4"
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh-command-feedback": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-message-feedback": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-llm": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-telemetry": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-anonymous-user-id": "0.1.7-rc.2",
-    "@deepseek-ai/cordis": "~4.0.4"
+    "@deepseek-ai/dsh-command-feedback": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-message-feedback": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-anonymous-user-id": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-otel": "0.2.0-rc.2",
+    "@deepseek-ai/cordis": "~4.0.4",
+    "@deepseek-ai/dsh-session-telemetry": "0.2.0-rc.2"
   },
   "devDependencies": {
     "@deepseek-ai/cordis-plugin-logger-console": "~1.0.4",
     "@deepseek-ai/cordis-plugin-loader": "~1.0.5",
-    "@deepseek-ai/dsh-app-boot": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-bash-local": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-command-feedback": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-message-feedback": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-loader-smoke": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-llm": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-checkpoint-policy": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-persistence-jsonl": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-telemetry": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-anonymous-user-id": "0.1.7-rc.2",
+    "@deepseek-ai/dsh-app-boot": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-bash-local": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-command-feedback": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-message-feedback": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-loader-smoke": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-checkpoint-policy": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-persistence-jsonl": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-session-telemetry": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-subprocess-local": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-anonymous-user-id": "0.2.0-rc.2",
     "@deepseek-ai/cordis": "~4.0.4",
-    "@deepseek-ai/dsh-http-proxy": "0.1.7-rc.2",
-    "@deepseek-ai/dsh-subprocess-local": "0.1.7-rc.2"
+    "@deepseek-ai/dsh-http-proxy": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-otel": "0.2.0-rc.2"
   }
 }