skills.rest
boundless-xyz
boundless-xyzOFFICIAL
Explore all skills by this author →
GitHub

ops-query

Query on-chain indexer data, broker telemetry, and CloudWatch logs to identify production incident root causes.

195|172|Updated Sep 25, 2024
Search Tags:#logs#telemetry#investigate#correlation#indexer#operational
One-click install
npx skills add https://github.com/boundless-xyz/boundless --skill ops-query
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ops-query
Source: https://github.com/boundless-xyz/boundless/tree/main/.claude/skills/ops-query
Command: npx skills add https://github.com/boundless-xyz/boundless --skill ops-query

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Boundless operators need a reliable way to diagnose production issues by cross-referencing on-chain indexer data, broker telemetry, and CloudWatch logs. This skill provides a structured workflow to surface root causes, correlate events across sources, and guide remediation on live networks.

Core Features & Use Cases

  • Cross-source investigations across indexer, telemetry, and logs to pinpoint the cause of failures, slashes, and skipped orders.
  • Setup guidance including required secrets and labels, plus optional data sources for deeper analysis.
  • Reusable playbooks leveraging the pre-built investigations under references to accelerate triage.

Quick Start

Start by selecting a network and run the ops-query workflow to gather indexer, telemetry, and log data for an end-to-end investigation.

Frequently Asked Questions about ops-query

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

FAQPage Schema
How do I investigate why slashings occurred on a production network?▼

To investigate slashings, this skill cross-references on-chain indexer data, broker telemetry, and CloudWatch logs to pinpoint root causes. It follows the OPS-SKILL suite setup, requiring access to network_secrets.toml and labels to correlate cross-source events.

What's the best way to correlate broker telemetry with on-chain indexer data?▼

Correlating broker telemetry with on-chain indexer data is done by querying both sources alongside CloudWatch logs to uncover root causes of failures. This structured workflow surfaces correlated events to guide remediation on live production and staging networks.

Do I need network_secrets.toml to query CloudWatch logs and indexer data?▼

Yes, you need network_secrets.toml and labels to query CloudWatch logs and indexer data. These setup steps from the OPS-SKILL suite are required to enable cross-source investigations across telemetry, indexer, and log data.

Can I use this skill to diagnose prover or service failures on staging networks?▼

Yes, you can use this skill to diagnose prover or service failures on staging networks. It applies to both production and staging environments, cross-referencing indexer data, broker telemetry, and CloudWatch logs to uncover root causes.

How does correlating market events with broker telemetry work?▼

Correlating market events with broker telemetry works by cross-referencing on-chain indexer data and CloudWatch logs to uncover root causes. This skill queries multiple data sources to identify production incidents and guide remediation on live networks.

Related Skills

Explore More Data & Analytics Skills→
Current-cmdCurrent-cmd

ops-query

Cross-references indexer data, broker telemetry, and CloudWatch logs to diagnose operational issues.

Community
Advanced
DaBigHomieDaBigHomie
1

problem-record-creation

Create ITSM Problem Records from incident reports with root causes and remediation plans.

Community
Advanced
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
redhat-etredhat-et
1

investigate-incident

Investigate platform incidents by gathering evidence and generating root cause documentation.

Official
Advanced