For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
      • Config targeting
      • Monitor config performance
      • Understand AI impact with AI Insights
      • The trends explorer
      • Manually instrument LLM spans
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • AI insights page
  • Trends
  • Quick stats
  • Configs and variations
  • Alerts
  • Instrumentation requirements
  • Choose a view
AgentControlDeliver and monitor configs

Understand AI impact with AI Insights

Was this page helpful?
Previous

The trends explorer

Next
Built with

Overview

This topic explains how to use AI insights to understand the impact of AgentControl configs by analyzing metrics across your project. AI insights provides a project-level view across configurations, models, and targeting rules. Use it to identify changes, compare configurations, and determine which configurations, models, or variations are driving results and their impact on performance and outcomes.

Use AI insights to:

  • Detect changes in cost, usage, and quality metrics
  • Identify regressions after updates
  • Compare performance across configs, models, and providers
  • Analyze trends over time and understand how changes affect performance
  • Investigate specific configs and recent changes
  • Establish consistent, organization-wide practices for evaluating AI model performance

To analyze performance for a single config, use the Monitoring tab.

AI insights page

The Insights page provides a unified, aggregated view of metrics across your configs. It includes time series charts, summary metrics, and a configuration-level table so you can review performance, identify changes, and understand their impact. All components reflect the selected time range and filters.

Use the controls at the top of the page to select a metric view, group results, filter configurations, and adjust the time range.

To open the Insights page:

  1. Navigate to your project.
  2. In the left navigation, expand AI, then select Insights.

The AI insights page showing trends, quick stats, and configurations table.

The AI insights page showing trends, quick stats, and configurations table.

Use this page to monitor performance and investigate changes across your configs. A typical workflow includes:

  1. Use the trends view to analyze changes over time and understand how updates affect performance.
  2. Review quick stats to identify changes in key metrics.
  3. Use the configs and variations table to compare configurations and identify which require further investigation. This helps you understand what changed and decide whether to act.

Alerts highlight changes in key metrics so you can identify where to investigate without reviewing each configuration individually.

Trends

The trends view displays metrics as time series charts so you can compare performance and understand how metrics change over time across configurations. You can group results by config, model, provider, or agent graph, including multi-agent workflows. You can analyze metrics such as token usage, latency, satisfaction, error rate, and evaluation scores over time.

The trends view showing time series charts and grouping controls.

The trends view showing time series charts and grouping controls.

Use the trends view to track changes over time and understand their impact on performance. Apply filters to focus your analysis on specific configurations or models.

You can also review changes to prompts, models, and targeting rules alongside performance metrics to understand how updates affect cost, latency, or satisfaction.

Quick stats

Quick stats summarize key metrics, including active configs and experiments, average satisfaction, and cost.

Quick stats showing active configs, experiments, satisfaction, and cost.

Quick stats showing active configs, experiments, satisfaction, and cost.

Use quick stats to identify changes in these metrics and determine where to investigate further. These changes may reflect shifts in performance and impact.

Configs and variations

The configs and variations table shows metrics for each config, including generations, token usage, satisfaction, latency, error rate, model and provider, and experiment status.

Table showing cost, generations, tokens, satisfaction, and model.

Use this table to compare configurations and identify differences in metrics that require further investigation.

Alerts

AI insights includes system-generated alerts for changes in key metrics. Use alerts to determine which configurations are driving changes and require further investigation.

Alerts provide a proactive way to monitor performance by highlighting configurations with recent changes so you can focus your investigation. Each alert includes the affected config and details about the change.

Instrumentation requirements

AI insights depends on metrics recorded from your application.

To populate insights, use a LaunchDarkly AI SDK to evaluate configs and record generation metrics such as latency, token usage, success, and error. You can also record evaluation metrics using judges.

If your application does not record metrics, the Insights page may not display data.

Choose a view

Use the following guidance to select the appropriate view:

  • Use AI insights to monitor metrics and identify changes across configurations.
  • Use the Monitoring tab to analyze performance for a single config and its variations.

These views support different levels of analysis, from investigating a single config to understanding patterns across configurations.