error-debugging-error-trace

Implements error tracking, structured logging, and alerting for production applications.

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill error-debugging-error-trace-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-debugging-error-trace
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/error-debugging-error-trace
Command: npx skills add https://github.com/monang404/lunawave --skill error-debugging-error-trace-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production systems often lack visibility into failures, making it hard to detect, group, and resolve errors before users are impacted. This Skill guides the implementation of comprehensive error monitoring so teams can identify and triage issues quickly. ## Core Features & Use Cases - Error Tracking Integration: Set up Sentry or custom error tracking services with fingerprinting, sampling, and sensitive-data sanitization. - Structured Logging & Alerting: Implement JSON structured logging with Winston/Elasticsearch and configure severity-based alert rules routed to Slack or PagerDuty. - Error Grouping & Recovery: Deduplicate errors via normalized fingerprinting and fuzzy matching, plus automatic recovery with retry and circuit breaker strategies. - Use Case: A backend team notices recurring production crashes with no clear pattern. Use this Skill to analyze the codebase's error handling, integrate Sentry with custom fingerprinting, and configure alert rules so similar errors are grouped and the on-call engineer is notified within minutes. ## Quick Start Ask the assistant to analyze the current project's error handling and set up error tracking with structured logging and alert rules.

Frequently Asked Questions about error-debugging-error-trace

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

FAQPage Schema
How do I set up error tracking with Sentry in Node.js?▼

Initialize Sentry with your DSN, environment, and release, then add integrations for HTTP, Express, and databases. Use beforeSend hooks to filter sensitive data and custom fingerprinting to control how errors are grouped.

How to implement structured logging in a production application?▼

Use a framework like Winston with JSON formatting, timestamps, and error stack capture. Route logs to files with rotation for all environments and add an Elasticsearch transport for production log aggregation and search.

What is error fingerprinting and grouping?▼

Error fingerprinting generates a hash from the error type, normalized message, and stack location so identical errors group together. Normalization replaces dynamic values like numbers, UUIDs, and URLs with placeholders, and fuzzy matching merges similar messages above a similarity threshold.

How do I configure alerts for high error rates?▼

Define alert rules with a condition, threshold, evaluation window, severity, and notification channels. Evaluate metrics against thresholds with cooldown periods to prevent alert fatigue, then route notifications to Slack, PagerDuty, or email.

When should I avoid adding error monitoring to a system?▼

Skip full monitoring setup when the system has no runtime or monitoring access, or when you only need a one-off bug fix. Also avoid logging secrets, tokens, or personal data, and use sampling to prevent overload in high-traffic production environments.