Changelog: Release Policies (Early Access), Observability in self-serve, and Logs and Traces improvements
Release Policies (Early Access)
We’ve introduced Release Policies in Early Access to make Guardian easier to use as the default release method, one of the top requests from Guardian customers.
The first version lets you:
- Define a scope for a policy (currently environments, with more options coming)
- Set a preferred release method (for example: “On production, Guarded Releases is the default”)
- Choose automatic or manual rollbacks
- Configure minimum sample size requirements (helpful for lower-traffic environments)
Release Policies will expand over the next few months alongside Guardrail Metrics, Global Metric Thresholds, and Release Templates, working toward our goal of zero-configuration Guardian rollouts.
Early Access is limited; reach out to your account team if you’d like to participate.
Observability now available in self-serve plans
Observability (Session Replays, Errors, Logs, Traces) is now included in Foundation self-serve plans on a usage-based model.
New customers can now add Observability directly in checkout — no sales conversation required — and existing customers will also have access.
Highlights:
- New trial onboarding flow for observability plug-ins and SDK setup
- Updated pricing page with a usage calculator
- Checkout support for usage-based or annual commit billing
With Observability in self-serve plans, teams can quickly debug issues, monitor performance, and get more value from feature flags — all without leaving LaunchDarkly.
See the documentation to get started, or if you are self-serve customer, add observability in the checkout
Logs and Traces improvements
We’ve shipped two major updates to make debugging and analysis in Logs and Traces faster and more powerful:
-
Live Mode: stream events in real time, no manual refresh required. Perfect for validating new instrumentation or monitoring fast-moving incidents.
-
Editable graph views: create and edit graphs directly in Logs and Traces without setting up a dashboard first. Switch graph types, run aggregations, and add up to two custom graphs per view.
Together, these updates help you move from “something looks off” to “here’s what’s happening and where” with fewer clicks, less overhead, and more confidence in what you’re seeing.
Learn more in the Logs and Traces documentation.
Other improvements
- Refreshed the Metric Groups UI with standardized components for a cleaner experience
- Added a new metric details tab showing configuration and connections upfront
- Introduced a tabbed connections table that splits connections across Experiments, Guarded Releases, and Metric Groups
- Multi-armed bandits dashboard refresh
- Refinements to the holdout builder and results view for Experimentation
- Improved metric accuracy by including events only from the selected environment
Bug fixes
- Updated error notifications for context kind creation
- Fixed a bug with newly created rules in AI Configs targeting
- Fixed display of empty stack traces
- Fixed metric preview edge cases where event data could show incomplete results