メニュー
Verify that OpenTelemetry traces are being collected and exported to X-Ray. Check trace health, find slow requests, investigate errors, and view service dependencies.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Check application logs from local Docker Compose or remote AWS CloudWatch environments. Supports local, staging, and production targets.
Deploy the Your Project Rails application to staging or production. Supports local builds via bin/deploy-staging and CI/CD via branch pushes.
Manage the local Docker Compose development environment. Supports start, stop, restart, and status operations.
Verify that Solid Queue background jobs are running properly. Checks worker health, recurring job execution, and optionally triggers a test job to prove end-to-end processing. Supports local, staging, and production targets.
Best practices for Rails Action Mailer. Use when writing new mailers, refactoring existing mailers, or when a mailer has inline business logic, missing previews, synchronous delivery, or mixed responsibilities. Applies patterns - single-responsibility mailers, parameterized mailers, deliver_later by default, mailer concerns, service delegation, previews, and structured testing.
Best practices for Rails Active Job with Solid Queue. Use when writing new background jobs, refactoring existing jobs, or when a job has mixed responsibilities, inline business logic, non-idempotent design, or missing error handling. Applies patterns - single-responsibility jobs, argument serialization, idempotent design, retry/discard strategies, queue management, recurring schedules, job concerns, and service delegation.
| name | ops-verify-telemetry |
| description | Verify that OpenTelemetry traces are being collected and exported to X-Ray. Check trace health, find slow requests, investigate errors, and view service dependencies. |
| allowed-tools | ["Bash","Read"] |
Verify that OpenTelemetry traces are being collected and exported to AWS X-Ray in the specified environment.
Target environment: $ARGUMENTS (expected: staging or production; default: staging)
| Environment | Profile |
|---|---|
| staging | your-project-staging |
| production | your-project-production |
aws sts get-caller-identity --profile <profile>
If expired: aws sso login --profile <profile>
Run the health subcommand to get trace count and sample traces from the last 5 minutes:
bin/verify-telemetry health <profile>
This confirms that the ADOT sidecar is receiving spans from the application and forwarding them to X-Ray.
Run the services subcommand to view the dependency map:
bin/verify-telemetry services <profile>
Verify that the your-project-<env> service appears in the graph and its downstream dependencies (MySQL, external APIs) are visible.
Based on user request or anomalies found in previous steps:
Slow requests (response time > 1s):
bin/verify-telemetry slow <profile>
5xx faults:
bin/verify-telemetry errors <profile>
Specific trace detail:
bin/verify-telemetry trace <trace-id> <profile>
Summarize findings in a table:
| Check | Result |
|---|---|
| AWS session active | Yes/No |
| Traces collected (last 5 min) | Count |
| Service graph populated | Yes/No (list services) |
| Slow requests (last hour) | Count |
| 5xx faults (last hour) | Count |
If any check fails, provide the specific error output and a recommended next step.
Verify telemetry now for the specified environment.