dropthejase bolts a flight recorder onto the AI

If you're running a Mike-derived agent in production, you can now see exactly what it did on every request - not guess from log lines.

infrastructure

The hardest question about any AI system in production is what it actually did: which requests failed, which model calls or tool runs went sideways. dropthejase wired this fork into CloudWatch, Amazon's monitoring service, so every request now reports its outcome as a tracked figure you can alarm on, and the route it took gets logged plainly.

The bigger move is turning on span-level tracing - a record of the individual steps inside a single request, the model calls and tool executions in sequence, so you can follow the chain instead of stitching it together after the fact. It's sampled lightly by default to keep monitoring costs down, with a documented dial to push it to full coverage when you need it.

So what Anyone running this agent in production who has to prove reliability - or debug it at 2am - gets that visibility without building a separate tracing system.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from dropthejase/louis, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
38adc057 feat(api): log HTTP status code and emit per-status CloudWatch metric Jason Lee 2026-05-13 ↗ GitHub
7b65f67e feat(observability): enable CloudWatch Transaction Search and tighten AgentCore IAM Jason Lee 2026-05-15 ↗ GitHub
commit body
- Split CloudWatchLogs policy into three statements scoped to log-group,
  log-stream, and describe-all per AWS docs (removes over-broad log-group:* wildcard)
- Add CfnResourcePolicy granting xray.amazonaws.com write access to aws/spans
  and /aws/application-signals/data log groups
- Add CfnTransactionSearchConfig at 5% indexing for representative trace sampling
4d660176 docs(readme): add Observability section and Transaction Search sampling config note Jason Lee 2026-05-15 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-354.md from inside the repo you want the changes in.

⬇ Download capture-thread-354.md