Source: github.com/langfuse/langfuse/releases/tag/v4.72.0
The release lets Langfuse send alerts, project notifications and prompt changes to PagerDuty, with the routing key set on the automation. AI Gateway spans are now attributed to their gateway API key and service during ingestion, and self-hosted instances report AI Gateway request counts through telemetry. Service key user IDs now default to the key name.
On the evaluation side, filter conditions can now be applied at the trace level. The AI Gateway settings gained an analytics tab, and the web app received AI Gateway onboarding. An obsolete managed evaluator catalog was removed.
Fixes cover topic grouping and tooltips, double counting of the cache-write TTL breakdown in generic gen_ai usage mapping, and model price reads that accept any usage key. Dependencies including follow-redirects, @hono/node-server, qs and dd-trace were also updated.
Why it matters if you build agents
Teams that already run Langfuse can route alerts and prompt change notices into PagerDuty by setting a routing key on an automation. Evaluation filters can now match on trace-level conditions, which may simplify setups that previously needed workarounds. If you read cost figures from generic gen_ai usage data, check them after upgrading, since the cache-write TTL double counting is fixed.
Get stories like this every weekday
One short email with the day's agent tooling news.