observability-debugging

Correlate traces, metrics, and logs to debug SEA-Forge services.

1|Updated Oct 1, 2025
One-click install
npx skills add https://github.com/GodSpeedAI/SEA --skill observability-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observability-debugging
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/observability-debugging
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill observability-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug SEA-Forge services by correlating traces, metrics, and logs to quickly identify bottlenecks, failures, and misconfigurations in distributed workloads.

Core Features & Use Cases

  • Unified telemetry: traces, metrics, and logs from SEA-Forge components are collected and correlated for end-to-end visibility.
  • Incident response: accelerate root-cause analysis during production incidents with guided debugging workflows.
  • Performance investigations: diagnose latency and throughput issues using distributed tracing and metrics dashboards.
  • Integration-ready: works with OpenTelemetry collectors, OpenObserve, and Logfire for centralized observability.

Quick Start

Set up OpenTelemetry instrumentation in SEA-Forge services, configure your backend (OpenObserve or Logfire), and access the observability dashboards to begin tracing a test request across components.

Frequently Asked Questions about observability-debugging

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

FAQPage Schema
How do I debug production incidents using distributed tracing and metrics?

Debug production incidents by correlating distributed tracing, metrics, and logs from SEA-Forge services to quickly identify bottlenecks and failures. Guided debugging workflows accelerate root-cause analysis during active production incidents.

What is the best way to correlate traces, metrics, and logs for performance investigations?

Correlating traces, metrics, and logs provides unified telemetry for end-to-end visibility during performance investigations. This approach diagnoses latency and throughput issues across SEA-Forge components using distributed tracing and metrics dashboards.

Do I need OpenTelemetry instrumentation to use observability debugging?

Observability debugging requires OpenTelemetry instrumentation in SEA-Forge services, a compatible backend like OpenObserve or Logfire, and access to service telemetry. Set up instrumentation and configure your backend to begin tracing test requests.

Can I use OpenObserve or Logfire as a backend for collecting service telemetry?

OpenObserve and Logfire are compatible backends for collecting service telemetry in observability debugging workflows. Integration with OpenTelemetry collectors and these centralized observability platforms enables end-to-end visibility across SEA-Forge deployments.

Why does my distributed tracing workflow fail to show end-to-end visibility across components?

Distributed tracing workflows fail to show end-to-end visibility when SEA-Forge services lack proper OpenTelemetry instrumentation or backend configuration. Ensure OpenTelemetry collectors are correctly set up and connected to OpenObserve or Logfire dashboards.

Does observability debugging work for diagnosing latency issues in SEA-Forge deployments?

Observability debugging works for diagnosing latency and throughput issues in SEA-Forge deployments by leveraging distributed tracing and metrics dashboards. It correlates telemetry data to pinpoint performance bottlenecks across distributed workloads.