skills.rest
lightdash
lightdashOFFICIAL
Explore all skills by this author →
Website𝕏@lightdash_devsGitHub

debug

Orchestrate PM2 logs, Spotlight traces, and browser automation to debug Lightdash issues.

6.0k|759|Updated Mar 19, 2021
Search Tags:#troubleshooting#logs#browser automation#debug#telemetry#traces#Lightdash
One-click install
npx skills add https://github.com/lightdash/lightdash --skill debug-lightdash
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/lightdash/lightdash/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/lightdash/lightdash --skill debug-lightdash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers diagnose issues in the Lightdash app by orchestrating PM2 logs, Spotlight traces, and browser automation.

Core Features & Use Cases

  • Live debugging: Collect and correlate PM2 logs, Spotlight telemetry, and browser sessions to reproduce issues.
  • Trace-driven investigation: Use trace IDs to drill into request flow, middleware, and backend queries.
  • Repro workflow automation: Script common debugging steps to reproduce user flows and capture state.

Quick Start

Start the development environment with docker-dev, then use the provided PM2 and Spotlight commands to begin debugging.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug Lightdash API bottlenecks using traces?▼

Debug Lightdash API bottlenecks by using Spotlight traces to drill into request flows, middleware, and backend queries. This skill correlates telemetry data to identify performance issues across local and CI environments.

Can I reproduce user flows for debugging with browser automation?▼

Yes, you can reproduce user flows for debugging by scripting browser automation sessions. This skill captures browser-based state to correlate frontend actions with backend behavior during issue investigation.

How do I collect PM2 logs for troubleshooting Lightdash?▼

Collect PM2 logs for troubleshooting Lightdash by orchestrating log collection alongside Spotlight telemetry and browser sessions. This process correlates backend logs with frontend actions to reproduce issues.

What is the best way to correlate frontend actions with backend behavior in Lightdash?▼

The best way to correlate frontend actions with backend behavior in Lightdash is by orchestrating PM2 logs, Spotlight traces, and browser automation. This skill provides deterministic debugging workflows to map frontend events to backend queries.

Do I need docker-dev to start debugging the Lightdash app?▼

Yes, you need to start the development environment with docker-dev before using the provided PM2 and Spotlight commands. This setup establishes the local environment required to begin the debugging workflow.

How does trace-driven investigation work for local and CI environments?▼

Trace-driven investigation works by using trace IDs to look up request flows across local and CI environments. This skill structures trace data to help you drill into middleware and backend queries deterministically.

Related Skills

Explore More Software Engineering Skills→
bRRRITSCOLDbRRRITSCOLD
2

devex

Automate local development environment setup with Docker containers and task runner commands.

Community
Intermediate
VictoriaMetricsVictoriaMetrics
45

vm-trace-analyzer

Analyze VictoriaMetrics query traces to identify bottlenecks and generate structured performance reports.

Official
Advanced
roundpilotroundpilot
53

browser-testing

Automate UI verification with screenshots, DOM inspection, and user flow recording.

Community
Intermediate
thesammykinsthesammykins

observability-sentinel

Instrument applications with OpenTelemetry and structured JSON logs.

Community
Advanced