multi-service-debug

Name: multi-service-debug
Availability: InStock
Author: dseirz-rgb

Correlate logs and traces to diagnose cross-service failures between Vercel and Cloud Run.

Updated Dec 29, 2025

Search Tags:#debugging #cloud #traceability #distributed-systems #log-analysis #web-services

Ready to run

npx skills add https://github.com/dseirz-rgb/worker --skill multi-service-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multi-service-debug
Source: https://github.com/dseirz-rgb/worker/tree/main/.kiro/skills/multi-service-debug
Command: npx skills add https://github.com/dseirz-rgb/worker --skill multi-service-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose cross-service failures that occur across a Vercel frontend and Cloud Run backends by unifying observability and debugging workflows.

Core Features & Use Cases

Cross-service debugging workflows: orchestrates log aggregation and trace correlation across frontend and backend services.
Global visibility: enables end-to-end request tracing and root-cause analysis for distributed issues.
Collaborative remediation guidance: provides structured steps and recommendations to resolve inter-service communication problems.

Quick Start

Prompt the AI to start a cross-service debug session. Provide the observed symptoms, affected services, and any trace IDs you have, and request a chained log analysis from the frontend (Vercel) to the backend (Cloud Run). Example: "Diagnose a failing request that travels from Vercel to Cloud Run; generate a trace chain, identify the failing hop, and propose fixes."

Frequently Asked Questions about multi-service-debug

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

FAQPage Schema

How do I debug cross-service failures spanning Vercel and Cloud Run?▼

Cross-service debugging for Vercel and Cloud Run requires correlating frontend and backend logs using trace IDs. This Skill unifies observability by aggregating logs, generating a distributed trace chain, and pinpointing the failing hop across services.

What is distributed tracing and when do I need it for web services?▼

Distributed tracing tracks a single request across multiple web services using trace IDs. You need it when a failure spans both frontend and backend environments, making it impossible to diagnose the root cause from isolated logs alone.

How do I perform root-cause analysis for distributed systems with trace IDs?▼

Root-cause analysis with trace IDs involves chaining log entries from the frontend to the backend to identify the failing hop. This Skill orchestrates that log aggregation and provides structured remediation guidance to resolve the inter-service communication issue.

Do I need frontend and backend logs to diagnose issues across Vercel and Cloud Run?▼

Yes, diagnosing issues across Vercel and Cloud Run requires access to both frontend and backend logs. You must also provide observed symptoms, affected services, and any available trace IDs to enable accurate log correlation and failure detection.

What's the best way to correlate logs between a Vercel frontend and a Cloud Run backend?▼

The best way to correlate logs between Vercel and Cloud Run is by matching trace IDs across both environments. This Skill automates that correlation, enabling end-to-end request tracing and structured remediation steps for inter-service failures.

Why does my Vercel to Cloud Run request fail without a clear error in the frontend logs?▼

Requests from Vercel to Cloud Run often fail without frontend errors because the exception occurs in the backend. You need cross-service log analysis with trace IDs to correlate the distributed logs and expose the backend exception causing the frontend failure.