---
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

Calibration fails if your data sources have no telemetry for what you describe, so pick one service or job that’s sending data now, and select the **Datasources** that contain its telemetry. If you’re not sure what has data, the hands-on path includes an optional step that runs a query in **Explore** to list the Prometheus jobs that are up.

## Name it so you can find it later

In **Name**, enter the service or check you want to watch, as a name you’ll recognize in the Watchers list.