skills/searching-datadog-logs/SKILL.md
Search and analyze Datadog logs and metrics using API for cupixworks-api and cupixworks-worker services. Use when debugging errors, investigating issues, searching logs, analyzing worker jobs, checking Sidekiq logs, querying metrics, or finding specific log entries by class/function names. Supports error/warn/info log levels with 14-day retention for logs.
npx skillsauth add olion500/skills searching-datadog-logsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Search and analyze logs/metrics from Datadog for cupixworks services.
# Logs — run with --help for all options
npx -y bun ${SKILL_DIR}/scripts/search-logs.ts -- --help
# Metrics — run with --help for all options
npx -y bun ${SKILL_DIR}/scripts/query-metrics.ts -- --help
cupixworks-api, cupixworks-worker)은 실제 repo 이름(tesla)과 다름. finding-repositories 스킬을 반드시 참고.now-14d 이상 시간 범위 요청 — 빈 결과만 나옴cupixworks-api → tesla repo임. finding-repositories 참고@class/@function 태그를 기대 — 최근 코드에만 있음. 키워드 검색으로 대체무엇을 찾는가?
├─ 특정 에러 조사
│ → -q "service:cupixworks-api status:error" -f "now-1h"
│ → 에러 메시지가 있으면: -q 'service:cupixworks-api "ErrorMessage"'
│
├─ 특정 클래스/워커 추적
│ → -q "service:cupixworks-worker @class:WorkerClassName" -f "now-24h"
│ → @class 태그 없으면: -q 'service:cupixworks-worker "WorkerClassName"'
│
├─ 특정 ID 관련 로그
│ → -q "service:cupixworks-worker (613263 OR 613260)" -f "now-24h"
│
├─ Datadog URL에서 같은 검색 재현
│ → --url "https://app.datadoghq.com/logs?query=..."
│
└─ 성능/트렌드 확인
→ query-metrics.ts 사용
→ -q "avg:system.cpu.user{service:cupixworks-api}" -f "1h"
# 에러 검색
-q "service:cupixworks-api status:error"
-q "service:cupixworks-worker status:error"
# 클래스/함수별 (최근 코드만)
-q "service:cupixworks-api @class:ClassName @function:method_name"
# 키워드 (구 코드 포함, 더 넓은 범위)
-q 'service:cupixworks-api "ActiveRecord::RecordNotFound"'
# 복수 ID
-q "service:cupixworks-worker (613263 OR 613260)"
# warn 레벨
-q "service:cupixworks-api status:warn"
avg:system.cpu.user{service:cupixworks-api}
avg:system.mem.used{service:cupixworks-api}
sum:rails.request.count{service:cupixworks-api}.as_rate()
sum:rails.request.errors{service:cupixworks-api}.as_rate()
avg:postgresql.query.time{service:cupixworks-api}
| Item | Value |
|------|-------|
| Services | cupixworks-api (Rails API), cupixworks-worker (Sidekiq) |
| Repository | 둘 다 tesla repo |
| Retention | 14일 |
| Log Levels | error, warn, info (debug 없음) |
| Tags | @class, @function (최근 코드만) |
| Credentials | DATADOG_API_KEY, DATADOG_APP_KEY (via just claude) |
| 증상 | 원인 | 해결 |
|------|------|------|
| 빈 결과 | 14일 초과 or 잘못된 service 이름 | 시간 범위 확인, service 필터 확인 |
| 빈 결과 | @class 태그 없는 구 코드 | 키워드 검색("ClassName")으로 대체 |
| 너무 많은 결과 | 필터 부족 | @class, status:error, 시간 좁히기 |
| pagination 필요 | limit 초과 | --cursor 사용 (스크립트가 cursor 출력함) |
development
Search and query Elasticsearch/Kibana database models using curl API. Use for querying database models, searching Kibana indices, checking Elasticsearch data, investigating data in Kibana, finding records by ID, searching documents. Supports multiple environments (dev, qa, stage, production-us, production-au, production-eu).
tools
Create, update, search, transition, link, and read comments on Jira issues via CLI. MUST use this skill whenever the user pastes or mentions any atlassian.net URL (Jira issues, Confluence pages, focusedCommentId links, board links — anything from *.atlassian.net). Also use for: TSLA-* ticket references, JQL searches, issue status changes, reading comments, creating bugs, updating descriptions. This is the ONLY way to interact with Jira/Atlassian — there is no MCP Atlassian available.
development
Search Cupix Watch (Kibana/Elasticsearch) application logs at watch.cupix.com. Use when the user asks to search logs, find errors, debug processing issues, or investigate service behavior. Triggers on keywords like "log", "watch", "kibana", "error log", service names (skat, pano, api, worker, vista), or mentions of cupix processing pipelines.
development
Access Azure DevOps resources (PRs, builds, pipelines, releases, variable groups) for the Cupix organization. TRIGGER when: user pastes a dev.azure.com URL; user mentions Azure DevOps, ADO, az pr, az pipeline, build status, release status, or deploy status for Cupix projects; user asks about PR reviews, build logs, pipeline runs, or release progress. SKIP: general git questions not about Azure DevOps; GitHub-only workflows.