#Anthropic має бета-продукт Claude in Chrome але доступ до нього поки що обмежений.
Claude Code 비용, AWS로 완전히 통제하다
2026년 AI 개발 환경에서 Claude Code 비용 관리는 선택이 아닌 필수입니다. AWS CloudWatch, Lambda, DynamoDB를 활용한 Observability 플랫폼으로 사용량을 실시간 추적하고 평균 20~35%의 비용 절감 효과를 경험해 보세요.
#Claude_Code #AWS #Observability #AI_비용_관리 #CloudWatch #블로그 #ODOB
【Bedrock AgentCore Observability】AIエージェントのログをCloudWatchに出力しよう!
https://qiita.com/PDC-Kurashinak/items/161f7ffdbb382ce82a5d?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Filtering JSON Log Data in CloudWatch using the jsonParse Function
Today’s post is one of those “I’m writing this so I can copy & paste it later” ones. (And yes, that cover image is a log joke and was selected to intentionally scar anyone my generation)
I’ve spent a lot of time in AWS CloudWatch today monitoring a database query log while I do some performance testing. I was looking at a long list of log entries that included a query duration as part of a JSON response in the log’s @message content.
The jsonParse function in CloudWatch allows you to query data in the JSON content. In this case, I want to sort all the queries by a duration_ms attribute greater than 0. I also want to display the duration_ms as a field in the query’s output.
Use this query:
fields @timestamp, @message, @logStream, @log, jsonParse(@message) as js| display js.duration_ms, @timestamp, @message, @logStream, @log| filter js.duration_ms > 0| sort js.duration_ms desc| limit 1000and you get:
This allowed me to quickly find the slow running queries from JSON data in the log.
AWS障害対応の事後報告書を自動生成!CloudWatch Incident Reportsを実際に使ってみた
https://qiita.com/sh_fk2/items/14e5595e40fc3024c805?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items