# Configure Distributed Debugging and Tracing

Distributed failures are difficult to reproduce and correlate across services. This skill designs debugging, tracing, logging, profiling, and production diagnostics workflows.

## Install

```bash
npx skillstore add sickn33/distributed-debugging-debug-trace
```

## Metadata

- Status: approved
- Slug: sickn33-distributed-debugging-debug-trace
- Skillstore revision: r2
- Version status: missing
- Tree hash: 349f927b0d13221904be922761ac315b5fefed015c27e16475807d9ec34fa333
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/distributed-debugging-debug-trace
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-distributed-debugging-debug-trace
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-distributed-debugging-debug-trace/manifest

## Capabilities

- Identifies service boundaries, trace propagation points, and useful spans.
- Proposes local and remote debugging configurations for Node.js applications.
- Designs OpenTelemetry tracing with Jaeger export and correlation identifiers.
- Defines structured logging, sampling, source map, and profiling patterns.
- Creates production debugging safeguards using feature flags, tokens, and IP controls.
- Provides dashboard, IDE, troubleshooting, and team workflow guidance.

## Use Cases

- Trace a Microservice Failure: Map request flow, define spans, and correlate logs for a failure crossing several services.
- Standardize Team Debugging: Create consistent IDE, logging, source map, and profiling practices for a development team.
- Diagnose Production Latency: Plan sampled tracing and profiling that limits overhead and protects sensitive data.

## Prompt Templates

### Set Up Local Debugging

```
Create a local debugging setup for [runtime and framework]. Include IDE configuration, source maps, test debugging, and validation steps.
```

### Design Distributed Tracing

```
Design tracing for [services and protocols]. Define propagation, key spans, standard attributes, sampling, export, redaction, and coverage tests.
```

### Investigate a Production Incident

```
Analyze this incident evidence: [logs, traces, symptoms, and timeline]. Correlate signals, rank hypotheses, and propose low-risk diagnostic steps.
```

### Build a Secure Debugging Platform

```
Create a production debugging architecture for [environment]. Include authentication, authorization, encryption, audit logs, data minimization, sampling, retention, and emergency controls.
```

## Limitations

- Examples require adaptation to the application framework, deployment model, and security controls.
- The skill does not inspect live systems without access to logs, traces, configuration, or runtime data.
- Some playbook examples are unsafe until authentication, redaction, and output encoding are added.
- Generated configurations require dependency, performance, and production validation.

## Best Practices

- Define a diagnostic question before increasing log detail, trace sampling, or profiler duration.
- Allowlist telemetry fields and redact secrets, credentials, tokens, and personal data before export.
- Test trace continuity, access controls, overhead, retention, and shutdown behavior before production rollout.

## Anti Patterns

- Do not expose runtime evaluation, inspectors, heap snapshots, or debug routes without strong authentication and network isolation.
- Do not record complete request bodies, session identifiers, or arbitrary objects in logs and traces.
- Do not use verbose production debugging without sampling, time limits, audit records, and rollback controls.

## Security Audit

- Audited at: 2026-07-23T22:28:42.727\+00:00
- Summary: Most static findings are false positives caused by JavaScript template literals, explicit configuration reads, and ordinary profiler file output. Confirmed risks include unsafe dashboard rendering and debugger exposure. The playbook also contains unauthenticated runtime evaluation and sensitive telemetry patterns that require correction before publication.

## Stats

- Views: 128
- Downloads: 9
- Favorites: 0
- Popularity score: 0