ops-logs-query

Query AWS CloudWatch logs for Boundless services on prod and staging environments.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Current-cmd/TrustMeBRO --skill ops-logs-query-current-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-logs-query
Source: https://github.com/Current-cmd/TrustMeBRO/tree/main/.claude/skills/ops-logs-query
Command: npx skills add https://github.com/Current-cmd/TrustMeBRO --skill ops-logs-query-current-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Investigating production issues in Boundless services requires manually navigating dozens of CloudWatch log groups across environments and chains, which is slow and error-prone without knowing the naming conventions and query patterns. ## Core Features & Use Cases - Log Group Discovery: Dynamically find log groups for provers, slasher, distributor, order stream, order generator, and indexer services using naming conventions and prefix searches. - Time-Bounded Log Queries: Search logs by request ID, request digest, or error patterns using CloudWatch filter syntax with proper Unix millisecond time ranges and pagination. - Deployment Investigation: Detect recent deployments and container healthcheck failures when diagnosing fulfillment drops or prover downtime. - Use Case: A user reports a failed proof request. Use this Skill to find the right log group, filter by the request ID over the past hour, and check whether a recent nightly deployment caused a broker outage. ## Quick Start Ask the assistant to search the staging indexer logs for errors mentioning a specific request ID from the last hour.

Frequently Asked Questions about ops-logs-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search CloudWatch logs for a request ID?▼

Use aws logs filter-log-events with the log group name, start and end times in Unix milliseconds, and a filter pattern like "0xREQUEST_ID". Pipe the JSON output through jq to format timestamps and messages for readability.

How do I find CloudWatch log groups for a specific service?▼

Use aws logs describe-log-groups with a prefix like l-staging-84532, or filter with a query containing the service name such as indexer or slasher. Prover log groups follow the pattern /boundless/bento/<hostname> defined in Pulumi config files.

What AWS credentials are needed to query Boundless logs?▼

Read network_secrets.toml from the repo root and export the access key ID and secret access key from the [aws.prod] or [aws.staging] section, plus AWS_DEFAULT_REGION us-west-2. If the file is missing, follow the Boundless runbook to create it.

Why is my CloudWatch log query slow or returning no results?▼

Queries without time bounds are slow because log groups are high-volume. Always set --start-time and --end-time in Unix milliseconds, keep windows to minutes or hours, and verify you are querying the correct log group since services can span multiple groups.

How do I check if a recent deployment caused a prover outage?▼

Filter the bento prover log group for patterns like "Stopping Docker Compose" and "Starting Docker Compose" to find deployment events. Then search for "unhealthy", "failed to start", or "Exited" to detect container healthcheck failures after the deployment.

When should I not use this log querying skill?▼

Do not use it for debugging local code changes, reviewing pull requests, or investigating issues in the codebase itself. It is intended only for querying CloudWatch logs of deployed Boundless services on prod and staging environments.