Query and analyze live Aztec network logs from GCP Cloud Logging.
npx skills add https://github.com/HabibTorjmen/Blockchain --skill network-logs
Please help me install this Agent Skill. Skill: network-logs Source: https://github.com/HabibTorjmen/Blockchain/tree/main/aztec-packages/.claude/skills/network-logs Command: npx skills add https://github.com/HabibTorjmen/Blockchain --skill network-logs
It helps you quickly understand what is happening in live Aztec deployments by turning vague operational questions into targeted GCP Cloud Logging queries and log-based findings.
testnet and can target devnet, mainnet, or custom namespaces to isolate the right deployment.network-logs subagent using the required agent-file workflow.Ask: "has testnet started producing blocks in the last 10 minutes?"
High-intent search queries and answers about installing and using this skill.
To query Aztec network logs for block production, specify your target namespace (like testnet or devnet) and time range. The system delegates to a subagent that filters GCP Cloud Logging results by severity and timestamp to diagnose block generation issues.
Yes, you can filter GCP Cloud Logging results by pod-specific behavior and proving status. The system supports intent-driven investigations, allowing you to isolate proving duration, transaction failures, and specific pod activities across devnet, testnet, or mainnet namespaces.
Debugging Aztec transaction processing failures requires querying live network logs using a specified namespace and time window. The system parses your operational intent and delegates a targeted GCP Cloud Logging query to extract relevant error logs without guessing log contents.
The default time range for Aztec network observability queries is typically a 10-minute freshness window. This time-range scoping converts relative or absolute dates into timestamp filters to ensure fast debugging and precise log searches across the specified deployment namespace.
This tool works with both standard Aztec environments and custom namespaces. While it defaults to testnet, you can target devnet, mainnet, or specify a custom namespace to isolate the exact deployment you need to investigate for network observability.
fcakyonDiagnose GCP production issues with structured logging and query guidance.
buildworksaiCollect Prometheus metrics, Grafana dashboards, and structured logs for EUCORA.
hairyfQuery Bitcoin and Liquid network data via REST and WebSocket APIs.
kubonyQuery and filter Cloud Logging data across GCP projects using gcloud logging read.