# Have the dashboards read for you

Reads every dashboard in Datadog, Honeycomb, Grafana and Axiom, and reports only the series drifting from their own normal.

## The prompt

```
I want to do this: Go through our dashboards and tell me what's drifting from normal this week.

## Setup (skip if Polylane is already set up)

Read and follow https://polylane.com/auth.md for non-interactive signup and setup. Start by checking whether I am already signed in; reuse my account and workspace.

If the CLI is missing, bootstrap it without starting the interactive wizard:

curl -fsSL 'https://polylane.com/setup?ref=prompts' | bash -s -- --install-only

Then follow the guide through email verification, workspace selection, source connections, and MCP authentication. Ask me for an email code or OAuth consent only when needed. Verify each step; report pending setup instead of claiming success from installation alone.

## How to work

Over MCP: searchTools lists what this workspace exposes, with each tool's schema; call it first. runTool runs one tool, runCode chains several in one call and returns just the answer. search and execute cover the full Polylane REST API: threads, issues, investigations, autofixes, memories.
From the terminal: the polylane CLI wraps the same API, with structured output and non-interactive flags everywhere.
Reads always work. Write tools appear only if I have opted in, and every write is screened.

## Task: Have the dashboards read for you

Steps:
1. Enumerate the saved queries and dashboards across connected providers
2. Read each series against its own history: rhythm, not flat thresholds
3. Flag sustained drift and direction-of-worse moves; ignore blips
4. Cross-check flagged series against recent changes for a cause
5. Deliver the weekly read: what's drifting, since when, and what likely moved it

Ground every claim in data you actually pulled: the query, the log line, the change record. If the data is inconclusive, say so. Ask me before anything that writes.
```

## What it replaces

**The dashboards are watched by nobody.** Every team builds dashboards; no team stares at them. The drift that precedes the incident is on a chart someone made two years ago and nobody has opened since.

- Forty dashboards, zero viewers
- Drift visible for weeks before the alert fires
- "Normal" defined by whoever last looked

## What the agent does

1. Enumerate the saved queries and dashboards across connected providers
2. Read each series against its own history: rhythm, not flat thresholds
3. Flag sustained drift and direction-of-worse moves; ignore blips
4. Cross-check flagged series against recent changes for a cause
5. Deliver the weekly read: what's drifting, since when, and what likely moved it

## What you get

**Every chart read, every week** The dashboards finally have a reader. Drift gets surfaced while it's a trend, not a page, with the likely cause already attached.

Every prompt: https://polylane.com/prompts/

Get started with one command: `curl -fsSL https://polylane.com/setup | bash` installs the CLI, connects your coding agents, and creates the account.