@@ -298,9 +298,10 @@ Deprecation is used to inform developers that some APIs and tools are no longer
298298TensorRT-LLM collects anonymous telemetry data by default. This data is used
299299in aggregate to understand usage patterns and prioritize engineering efforts.
300300** This data cannot be traced back to any individual user.** No prompts,
301- user-identifying information, or persistent identifiers are collected. Any
302- deployment identifiers are ephemeral, randomly generated per deployment, and
303- not linked to users. The data we collect includes:
301+ outputs, model weights, model paths, tokenizer paths, user-identifying
302+ information, raw free-form configuration strings, or persistent identifiers are
303+ collected. Any deployment identifiers are ephemeral, randomly generated per
304+ deployment, and not linked to users. The data we collect includes:
304305
305306- Ingress point (e.g., LLM API, CLI, serve command)
306307- Deployment duration (via periodic heartbeats)
@@ -309,8 +310,10 @@ not linked to users. The data we collect includes:
309310- Parallelism configuration (TP/PP/CP/MoE-EP/MoE-TP sizes), quantization algorithm, dtype, KV cache dtype
310311- System information (OS platform, Python version, CPU architecture, CPU count)
311312- TRT-LLM version and backend
312- - Feature flags (LoRA, speculative decoding, prefix caching, CUDA graphs, chunked context, data parallelism)
313+ - Feature summary flags (LoRA, speculative decoding, prefix caching, CUDA graphs, chunked context, data parallelism)
313314- Disaggregated serving metadata (role and deployment ID)
315+ - Selected LLM API configuration values: parallelism, dtype, KV cache, scheduler, CUDA graph, and compile settings
316+ - Capture diagnostics for that payload: a schema checksum (for provenance), the count of captured fields, and whether any free-form value was skipped
314317
315318Telemetry is automatically disabled in CI and test environments.
316319
0 commit comments