error-tracking

Instrument Sentry v8 error and performance capture across services.

Updated May 10, 2025
One-click install
npx skills add https://github.com/adteco/glapi --skill error-tracking-adteco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/adteco/glapi/tree/main/.claude/skills/error-tracking
Command: npx skills add https://github.com/adteco/glapi --skill error-tracking-adteco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures every error and performance issue across controllers, workflows, cron jobs, and database queries is captured in Sentry v8 so nothing slips through unnoticed.

Core Features & Use Cases

  • Controller and route guards enforce BaseController and helper-based Sentry capture so exceptions never rely on console.error alone.
  • Workflow, cron job, and database instrumentation define mandatory span tracing patterns with context tags, sampling configuration, and error capture helpers.
  • Team-wide observability tracks Form and Email services with shared configuration, test endpoints, and integration checklists to keep releases compliant.

Quick Start

Apply the error-tracking patterns by importing instrument.ts first, wrapping operations with WorkflowSentryHelper or Sentry spans, and tagging each error path with the required context.

Frequently Asked Questions about error-tracking

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

FAQPage Schema
How do I implement Sentry v8 error tracking across Node.js services?

Sentry v8 error tracking across Node.js services requires importing instrument.ts, wrapping operations with WorkflowSentryHelper or Sentry spans, and tagging each error path with required context. This ensures controllers, cron jobs, workflows, and database operations capture every exception.

What is the best way to monitor cron jobs and database performance in Sentry?

Monitoring cron jobs and database performance in Sentry requires mandatory span tracing patterns with context tags, sampling configuration, and error capture helpers. WorkflowSentryHelper wraps these operations to ensure consistent instrumentation and complete observability.

Why does my Node.js controller bypass Sentry error capture?

Node.js controllers bypass Sentry error capture when they rely on console.error alone. Controller and route guards enforce BaseController and helper-based Sentry capture, ensuring exceptions never slip through unnoticed and maintaining consistent context tagging.

Can I use Sentry spans for database operations without losing context tags?

Sentry spans for database operations preserve context tags by applying mandatory span tracing patterns. Database instrumentation defines required context tagging, sampling configuration, and error capture helpers to maintain consistent observability across queries.

Does Sentry v8 require specific instrumentation for Node.js cron jobs?

Sentry v8 requires mandatory cron instrumentation for Node.js cron jobs. Workflow, cron job, and database instrumentation define mandatory span tracing patterns with context tags, sampling configuration, and error capture helpers to satisfy v8 coverage requirements.

What limitations exist when adding error handling to Node.js workflows?

Adding error handling to Node.js workflows requires importing instrument.ts first and wrapping operations with WorkflowSentryHelper or Sentry spans. Without consistent context tagging and mandatory span tracing, performance issues across services may slip through unnoticed.