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

# DRE Insights

> Measure DRE reliability, human-judged RCA accuracy, Pulse efficiency, and runbook readiness from one analytics workspace.

Open **DRE → Insights** to review how the complete response loop performs. The workspace separates operational speed from human-judged accuracy so a confident agent verdict does not count as a correct result by itself.

## Choose an insight view

| View              | What it answers                                                                          |
| ----------------- | ---------------------------------------------------------------------------------------- |
| Overview          | How quickly and reliably does DRE move through detection, investigation, and resolution? |
| Accuracy & trust  | How often do human verdicts confirm the RCA result?                                      |
| Pulse analysis    | How well does Pulse correlate Signals, suppress noise, and resolve Clusters?             |
| Runbook analytics | Which incidents have usable remediation coverage, and where are the gaps?                |

## Review reliability

Use **Overview** for stage timing, MTTR trends, recurring incidents, impact, and per-service reliability. A change in one stage can explain a change in the total response time, so review the stage timings before you attribute a regression to RCA.

## Judge accuracy with human verdicts

**Accuracy & trust** uses explicit human feedback about the investigation result. Agent confidence and the final disposition do not count as proof that the RCA was correct.

Use this view to answer:

* Which services or incident types receive enough human verdicts to measure?
* Where do operators reject or correct the proposed root cause?
* Is the amount of human feedback sufficient to support a decision?

When an operator disagrees with a diagnosis, they pick one reason: **wrong root cause**, **wrong service**, **fix wouldn't work**, **false positive**, or **something else**. Read the distribution before you change a prompt — wrong service points at topology or context, while fix wouldn't work points at remediation quality.

Treat a small sample as incomplete evidence. Review the underlying Incidents before you change an integration, prompt, or operational process.

## Find Detect and Resolve gaps

Use **Pulse analysis** for correlation yield, Cluster MTTR, Signals ingested, noise suppressed, and top noisy sources. Use **Runbook analytics** for coverage, executions, and missing procedures.

## Related

<CardGroup cols={2}>
  <Card title="Analyze Pulse" icon="pulse" href="/guide/pulse/analytics">
    Interpret correlation, suppression, volume, and Cluster MTTR.
  </Card>

  <Card title="Review RCA" icon="magnifying-glass" href="/guide/incident/root-cause-analysis">
    Understand the evidence and outcomes behind the accuracy results.
  </Card>

  <Card title="Manage runbooks" icon="book" href="/guide/incident/runbooks">
    Add procedures and control mutating commands.
  </Card>

  <Card title="Tune DRE behavior" icon="sliders" href="/guide/incident/settings">
    Change automatic RCA and re-investigation sensitivity.
  </Card>
</CardGroup>