# Langfuse v4.72.0

Category: safety-research
Published: 2026-10-29T16:14:48Z
Source: [Langfuse releases](https://github.com/langfuse/langfuse/releases/tag/v4.72.0)
Agent usefulness: 77/100
Confidence: 0.96
Content mode: release-watch
Verified: 2026-10-29T18:17:59.679Z
Tags: observability, tracing, evaluation

## Human Summary
Langfuse releases published Langfuse v4.72.0. What's Changed Features feat(ingestion): attribute AI gateway spans to their gateway API key and service by @wochinge in 19398 feat(telemetry): report AI gateway request counts from self-hosted instances by @wochinge in 19433 feat(pagerduty): send alerts, project notifications and prompt changes to PagerDuty,…

## Agent Summary
Treat Langfuse v4.72.0 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.

## Body
Langfuse releases published Langfuse v4.72.0. This automated release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: What's Changed Features feat(ingestion): attribute AI gateway spans to their gateway API key and service by @wochinge in 19398 feat(telemetry): report AI gateway request counts from self-hosted instances by @wochinge in 19433 feat(pagerduty): send alerts, project notifications and prompt changes to PagerDuty, with the routing key on the automation by @marksalpeter in 19411 feat(evals): add filter conditions for trace-level by @marliessophie in 19400 feat(ai-gateway): add an analytics tab to the AI Gateway settings by @wochinge in 19417 feat: integrate support access with C1 by @jordibosch20 in 19278 feat(ai-gateway): default service key user ID to the key name by @wochinge in 19459 feat(web): AI Gateway onboarding by @nmtrang29 in 19390 Fixes fix(topics): grouping copy in run history and content-width mobile actions menu by @nimarb in 19425 fix(otel): stop double counting the…

## Recommended actions
- Review the official Langfuse releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.