Changelog #111
Increased OTel attribute limits
CTO, Trigger.dev
We've significantly increased the OpenTelemetry (OTEL) attribute limits and made them fully configurable for both cloud and self-hosted environments.
What's changed
Increased default limits: Span and log attribute value limits have been raised from 1,024 bytes to 131,072 bytes (128KB) by default, giving you much more room for detailed telemetry data.
Smart truncation: In the Trigger.dev dashboard logs, attributes are still truncated to keep the UI performant, but the full data is preserved in your telemetry pipeline.
Full configurability: Self-hosters can now customize all OTEL limits using environment variables, while cloud users can request custom limits from our team.
Configuration options
For self-hosted deployments, you can now configure these environment variables:
# Attribute count limitsTRIGGER_OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT=256TRIGGER_OTEL_LOG_ATTRIBUTE_COUNT_LIMIT=256# Attribute value length limits (in bytes)TRIGGER_OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT=131072TRIGGER_OTEL_LOG_ATTRIBUTE_VALUE_LENGTH_LIMIT=131072# Event and link limitsTRIGGER_OTEL_SPAN_EVENT_COUNT_LIMIT=10TRIGGER_OTEL_LINK_COUNT_LIMIT=2TRIGGER_OTEL_ATTRIBUTE_PER_LINK_COUNT_LIMIT=10TRIGGER_OTEL_ATTRIBUTE_PER_EVENT_COUNT_LIMIT=10
For cloud users, these limits can be configured per-environment by the Trigger.dev team. Contact support if you need custom limits for your use case.
Why this matters
The small otel attribute value limits were causing issues when using Trigger.dev with 3rd party otel exporters, particularly Langfuse, because large AI JSON payloads were being truncated.
Installation
Make sure you update your @trigger.dev/sdk and trigger.dev CLI packages to the latest beta version 4.0.0-v4-beta.22:
# Install the latest beta version of the SDK and any other @trigger.dev/* packagespnpm add @trigger.dev/[email protected]# Use the latest beta version of the CLIpnpm dlx [email protected]