Grafana Learn
Sign in Sign up
Section 2 · Choose recurring work

Explain why each run needs explicit scope, a relative time range, and output criteria.

Estimated time: 1 min

Give every run the context it needs

Each run creates a dedicated conversation. The checkout summary needs a self-contained prompt rather than references such as “the service above” or “yesterday’s query.”

This example names the scope and the evidence expected in the result:

Summarize the last 24 hours for the checkout service. Use metrics-main for metrics and logs-main for logs. Describe request volume, error rate, and notable error messages. Include the time range and links to supporting evidence. Separate missing data from healthy results. Don’t change resources.

Prompt structure

Annotated checkout prompt identifying the service and relative time window, exact data sources, expected findings, supporting evidence, and guardrails. The full prompt appears above.

A relative window, such as “the last 24 hours,” stays relevant as the prompt repeats. Exact service and data source names reduce ambiguity, while explicit output criteria make the result easier to evaluate.