error-tracking

Capture runtime errors across services with Sentry v8 for unified monitoring.

Updated Nov 14, 2025
One-click install
npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill error-tracking-donaldshen27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/Donaldshen27/xtrend-vanilla/tree/main/.claude/skills/error-tracking
Command: npx skills add https://github.com/Donaldshen27/xtrend-vanilla --skill error-tracking-donaldshen27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive Sentry v8 error tracking and performance monitoring across project services, ensuring every error is captured and traceable for faster remediation.

Core Features & Use Cases

  • Centralized error capture across controllers, routes, cron jobs, and workflows
  • Performance tracing and context-rich insights across multiple services
  • Standardized integration patterns and helpers to accelerate adoption

Quick Start

Initialize Sentry in your service entrypoint, import the instrument.ts module first in cron jobs, and verify error capture with a quick test endpoint.

Frequently Asked Questions about error-tracking

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

FAQPage Schema
How do I enforce Sentry error tracking across multiple services?

Enforce Sentry error tracking by initializing Sentry in service entry points and applying consistent error-handling patterns across controllers, cron jobs, and workflows to capture all runtime errors with rich context.

What is the best way to capture runtime errors in cron jobs using Sentry?

Capture runtime errors in cron jobs by importing the instrumentation module first in the execution sequence, ensuring Sentry v8 traces and reports failures with standardized context across scheduled workflows.

Does Sentry v8 work with multi-service architectures for centralized error monitoring?

Sentry v8 works with multi-service architectures by standardizing integration patterns across controllers and database interactions, providing centralized error capture and performance tracing for faster remediation.

How do I verify error tracking instrumentation is working in my application?

Verify error tracking instrumentation by creating a quick test endpoint that triggers a runtime error, confirming the event appears in Sentry with the expected context and trace data from your service.

Why do I need to initialize Sentry in service entry points?

Initialize Sentry in service entry points to ensure the instrumentation loads before any controllers or workflows execute, preventing missed runtime errors and guaranteeing comprehensive error capture.

Can I use Sentry for performance tracing and not just error tracking?

Sentry v8 provides performance tracing alongside error tracking, delivering context-rich insights across multiple services to monitor both runtime failures and application performance bottlenecks.