Read the Home briefing

Use the production briefing to find important changes, understand coverage, and open the evidence behind each finding.

Home is the starting point for a project's current operating picture. It combines a period briefing, important metrics, and evidence-backed findings so you can decide what deserves attention before opening a broader dashboard.

Confirm the scope first

Check the active project, period, and comparison before interpreting the briefing. The same movement can mean something different when traffic volume, workflow mix, model, release, or evidence coverage changed.

The current daily period can still be preparing while new telemetry arrives. Historical periods are read-only snapshots: navigate between them to compare what Neatlogs knew during each completed period.

Read the briefing in order

1. Lead finding

The lead title and summary state the most important supported conclusion for the period, or indicate that no material concern was found. This is a prioritization aid, not a substitute for the cited evidence.

2. Comparison

Use the comparison with the prior period to tell a new change from a persistent condition. Confirm that both periods cover comparable traffic before treating the direction as improvement or regression.

3. Metrics

Move through the metric cards for available quality and operational signals. Read totals beside rates and per-run values. A higher cost total with stable cost per run can simply mean traffic grew.

4. Findings

Findings are grouped so related observations can be reviewed together. Open each material finding to inspect its linked traces, incidents, and alerts. If the supporting population is too small or incomplete, treat the conclusion as provisional.

5. Data coverage

Read coverage notes before relying on silence. A quiet period may mean no supported concern was found, but it can also reflect partial ingestion, a short window, or evidence that is still being prepared.

Use attention items as a work queue

Home can surface setup and operational actions in addition to the briefing, including:

  • incidents that need review;
  • detection spikes or noisy alerts;
  • instrumentation gaps and missing traces;
  • prompts to invite teammates, configure the first detection, or manage prompts;
  • a direct path into AI Search.

Open the owning surface to complete the work. Home summarizes and routes; it does not replace the incident record, detection configuration, alert policy, Eval result, or trace detail.

Handle preparation and failure states

StateWhat to do
Briefing is preparingWait for the current-period job and return later; other product evidence remains available
Retry is offeredRetry the current briefing, then check ingestion if it fails again
No findingsConfirm coverage and traffic before concluding that nothing happened
Historical period has limited evidenceUse it as a snapshot and open the underlying data that remains available
Metric and finding disagreeCompare their scope, time boundary, and source population

Move from summary to action

Use this sequence for a material finding:

  1. open the linked evidence;
  2. confirm the affected population and comparison;
  3. open the related incident, or investigate the evidence when the finding needs follow-up;
  4. investigate when the cause is unknown;
  5. create or tune a detection when the behavior can be defined repeatedly;
  6. verify the change against new production evidence.

Frequently asked questions

Is Home a real-time alert feed?

No. Alerts handle time-sensitive response policies. Home provides a period-level briefing and a prioritized path into the relevant evidence.

Can I edit a historical briefing?

Historical periods are read-only. Use their linked evidence to continue work in Incidents, Investigate, Detections, Alerts, or Evals.

Does “all clear” prove every run was correct?

No. It means the available supported evidence did not produce a material finding for that period. Always consider coverage and whether the relevant behavior has a detection or Eval.

Next step

Review incidents that need attention →

On this page

Ask Neatlogs AI

Answers from the docs

How can I help?

Ask anything about instrumenting, tracing, or the Neatlogs dashboard.