> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fiddler.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Executive Dashboard

> A cross-project overview of GenAI and ML health for organization leadership, with pre-aggregated metrics that outlive raw data retention.

<Note>
  The Executive Dashboard is currently in private preview and not yet available
  to all customers. Contact your Customer Success Manager for access.
</Note>

### Overview

The Executive Dashboard gives organization leadership a single, at-a-glance
view of GenAI adoption, quality, and cost across every application — without
stitching together per-application dashboards.

* **Top-line KPIs** — Total Apps, Active Apps, Total Traces, Total Spans,
  Errors, Sessions, and Evaluations Run over a selectable 7-day, 14-day, or
  30-day window.
* **Evaluator scores** — Average Quality alongside Answer Relevance, Context
  Relevance, RAG Faithfulness, Response Faithfulness, Conciseness, Prompt
  Safety, and PII Detection, aggregated across all applications.
* **Usage and latency** — Traffic and token-usage trends, Average Trace
  Latency, and P90 Span Latency.
* **Application Health Overview** — a per-application table (traces, average
  latency, tokens, average quality) with drill-down links into each
  application.
* **Period-over-period change** — each metric card shows the change versus
  the immediately preceding window of equal length.

### How metrics are captured

Executive Dashboard metrics are not computed from raw traces at page load.
Instead, Fiddler continuously pre-aggregates them into a dedicated **metric
store**:

* **Hourly aggregation.** Background jobs run every hour and summarize the
  most recently completed hour of traces, spans, and evaluator results into
  per-application metric values (counts, sums, averages, and latency
  percentiles). Coarser views — daily or weekly trends — are derived from
  these hourly values.
* **Metric history outlives raw data.** The metric store is retained
  independently of your raw trace retention policy. When raw traces and spans
  are deleted at the end of their configured retention period, the aggregated
  metric history remains, so long-range trends and period-over-period
  comparisons keep working.
* **Freshness.** Because aggregation runs hourly on completed hours, the most
  recent data point on the dashboard can lag real time by up to an hour.
  Evaluator scores that are produced asynchronously are incorporated by
  subsequent aggregation passes.
* **What is aggregated.** Only numeric metric values are stored in the metric
  store — counts, token totals, latency statistics, and evaluator score
  aggregates per application and hour. No prompt, response, or other span
  content is copied into it.

<Info>
  Period-over-period change compares the selected window against the window of
  equal length immediately before it — a 30-day view reads 60 days of metric
  history. Deltas appear once enough history has accumulated in the metric
  store.
</Info>

### Related

* [Dashboards overview](/observability/dashboards)
* [Creating dashboards](/observability/dashboards/dashboards-creating)