Choose the right dashboard
Choose an organization or project view, understand its scope, and move from aggregate signals to source traces and scorer results.
Noveum separates organization-wide reporting from project-specific investigation. Choose the view whose scope matches the question before interpreting a number.
Quick answer
| Question | Start here | Next evidence |
|---|---|---|
| What changed across the organization? | Organization Analytics | Explorer or All Traces with the same Performance project and date range. |
| Is one project receiving and evaluating data? | Project Overview | Project Traces, Datasets, ETL Jobs, Eval Jobs, or Runs. |
| Which scorer outcomes are healthy or failing? | Project Health | Scorer result, dataset item, and source trace. |
| Which project consumed traffic or credits? | Organization or project Usage | Project workflow and source telemetry for the same period. |
| What happened in one execution? | Project Traces or Explorer | The first unexpected span and its recorded attributes. |
Organization Analytics
Analytics combines cross-project Performance trends with organization Quality snapshots.
Use Performance to compare projects and time ranges for trace count, turns, latency, token usage, estimated cost, error rate, and model series. The project and date controls apply to Performance.
Use Quality to review the current organization evaluation snapshot. The visible project and date controls do not currently filter Quality. Keep that limitation in mind when comparing Quality with a project-specific view.
Read the complete definitions in Organization analytics.
Project Overview
Project Overview is the landing page for one application. Use it to confirm that the project exists and that recent tracing and evaluation assets are connected before opening a specialized workspace.
If a summary appears empty:
- verify the organization and project in the application shell;
- confirm the SDK is sending the expected project identifier;
- open Project Traces and widen the date range;
- confirm dataset association and ETL or eval job state;
- refresh snapshot-backed analytics when new data has just arrived.
Overview is an orientation surface, not the source of truth for one request or scorer result.
Project Health
Health aggregates scorer results for datasets associated with the project. Use dataset and display controls to compare coverage and failure patterns, then open the underlying result before acting.
Different counts represent different units:
- traces are recorded executions;
- dataset items are mapped evaluation cases;
- eval runs are job executions;
- scorer results are individual scorer and item outcomes.
For example, 36 items evaluated by 12 scorers can produce 432 scorer results. That is not 432 eval-job runs.
Usage
Usage pages answer consumption and allowance questions. Their scope and time model can differ from Analytics and Health. Do not compare values from separate pages unless organization, project, time window, unit, and snapshot time match.
Move from a signal to evidence
Continue with Projects, Runs, or The closed-loop workflow.