Find and close the observability gaps
Finds the routes with no logs or spans, then drafts the instrumentation in your own Honeycomb, Axiom or Sentry setup.
I want to do this: Which critical services have no logs or traces? Show the gaps and write the fixes. ## 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: Find and close the observability gaps Steps: 1. Read the critical services' routes in the connected repos 2. Map which ones log, which trace, and which swallow errors silently 3. Rank the gaps by the tier and traffic of the route they blind 4. Draft the instrumentation fixes in the repo's own logging style 5. Deliver the gap report with the draft changes ready for review 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.
You discover the missing log line mid-incident.
Coverage grew organically: the services someone instrumented are observable, the rest are hope. The gap always surfaces at the worst time, on the route that's currently failing.
- Debugging a route that logs nothing
- Errors swallowed by a catch block from 2023
- Instrumentation backlog that never beats feature work
One prompt, this much work. Every step on your real data.
- 1 Read the critical services' routes in the connected repos
- 2 Map which ones log, which trace, and which swallow errors silently
- 3 Rank the gaps by the tier and traffic of the route they blind
- 4 Draft the instrumentation fixes in the repo's own logging style
- 5 Deliver the gap report with the draft changes ready for review
The next incident has the logs it needs
Blind spots found and the fixes drafted in your own conventions, before the incident that needed them. Coverage becomes a fact, not a hope.
The quiet failure 
“Find things that look wrong but never alerted: error spikes, dead crons, growing queues.” Know the account 
“Map our AWS account: what's running, what depends on what, and what's critical?” Risky config 
“Find the risky configuration: public buckets, missing alarms, single points of failure.” The cron audit “List every scheduled job across our clouds and when each one last succeeded.” Read my dashboards 
“Go through our dashboards and tell me what's drifting from normal this week.” Query to check “Write the query for checkout error rate by region over 24 hours, and save it as a check.” Coverage gaps “Which routes swallow errors or log nothing? Show the gaps and the fixes.” The weekly read 
“Summarise what our telemetry says about last week: regressions, improvements, anything odd.” Watch this deploy “We're deploying checkout-api at 5pm. Watch the metrics after and flag anything that moves.” Onboard me “I'm new here. Walk me through the architecture: the critical path, the data stores, what talks to what.” Instrument the launch “payments-v2 ships next week. What instrumentation should it have before launch? Draft it.”
“Find things that look wrong but never alerted: error spikes, dead crons, growing queues.” Know the account “Map our AWS account: what's running, what depends on what, and what's critical?” Risky config “Find the risky configuration: public buckets, missing alarms, single points of failure.” The cron audit “List every scheduled job across our clouds and when each one last succeeded.” Read my dashboards “Go through our dashboards and tell me what's drifting from normal this week.” Query to check “Write the query for checkout error rate by region over 24 hours, and save it as a check.” Coverage gaps “Which routes swallow errors or log nothing? Show the gaps and the fixes.” The weekly read “Summarise what our telemetry says about last week: regressions, improvements, anything odd.” Watch this deploy “We're deploying checkout-api at 5pm. Watch the metrics after and flag anything that moves.” Onboard me “I'm new here. Walk me through the architecture: the critical path, the data stores, what talks to what.” Instrument the launch “payments-v2 ships next week. What instrumentation should it have before launch? Draft it.”