---
title: "Keep the scope narrow | Grafana Labs"
description: "Focus each watcher on one service or failure mode and the signals that need attention."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Keep the scope narrow

Focus the watcher on **one service or failure mode** and the signals that need attention. For example, watch checkout on its own rather than checkout, payments, and inventory together.

A checkout watcher is one service and one question: does checkout recover after a rollout, or does it stay broken?

## Pick something with live data

Assistant builds the watcher’s checks from the telemetry in the data sources you choose. If those data sources have no telemetry for what you describe, Assistant can’t build the checks. Pick one service or job that’s sending data now. If you’re not sure what has data, the hands-on learning path includes an optional step that lists the Prometheus jobs that are up.
