# full-stack-error-tracking-with-sentry

> Sentry integration for error tracking across Next.js, Python, and Firebase. PROACTIVELY activate for: (1) Setting up Sentry SDK, (2) Configuring error boundaries, (3) Adding custom context to errors, (4) Source map configuration, (5) Release tracking. Triggers: "sentry", "error tracking", "error boundary", "exception monitoring", "crash reporting", "source maps"

- Author: Robin Mestre
- Repository: robinmestre/skills-factory
- Version: 20260201125424
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/robinmestre/skills-factory
- Web: https://mule.run/skillshub/@@robinmestre/skills-factory~full-stack-error-tracking-with-sentry:20260201125424

---

---
name: full-stack-error-tracking-with-sentry
version: "1.0"
description: >
  Sentry integration for error tracking across Next.js, Python, and Firebase.
  PROACTIVELY activate for: (1) Setting up Sentry SDK, (2) Configuring error boundaries,
  (3) Adding custom context to errors, (4) Source map configuration, (5) Release tracking.
  Triggers: "sentry", "error tracking", "error boundary", "exception monitoring", "crash reporting", "source maps"
core-integration:
  techniques:
    primary: ["systematic_analysis"]
    secondary: ["structured_evaluation"]
  contracts:
    input: "none"
    output: "none"
  patterns: "none"
  rubrics: "none"
---

# Full-Stack Error Tracking with Sentry

This skill provides expertise in observability for the vibekit marketplace.

## Overview

Sentry provides real-time error tracking and performance monitoring across your full stack, enabling quick identification and resolution of issues.

## Key Concepts

- **Error Boundaries**: Catch and report React component errors
- **Source Maps**: Map minified code back to original source
- **Release Tracking**: Associate errors with specific deployments
- **Custom Context**: Add user, request, and business context to errors
- **Performance Monitoring**: Track transaction performance and bottlenecks

## Best Practices

1. Configure source maps for readable stack traces
2. Set up release tracking for deployment correlation
3. Add user context for error attribution
4. Use error boundaries in React components
5. Configure sampling rates appropriately for production

[Content to be expanded based on plugin_spec_agentient-observability.md specifications]