gs-santry-observability_skill

Overview

This skill adds Sentry observability tailored to Clean Architecture layers. It provides layer-specific error tracking, transaction and span tracing for Use Cases and repositories, and user context handling for actionable error reports. The goal is clear telemetry for domain, application, infrastructure, and presentation concerns.

How this skill works

Initialize Sentry with environment-aware sampling and global configuration. Wrap Use Case execution in transaction spans, create child spans for domain entity operations and repository calls, and set user context early in procedure chains so subsequent errors carry user metadata. Capture domain exceptions with tags, contexts, and mapped severity levels, and record breadcrumbs at key flow points.

When to use it

• You want per-layer error insights (domain, application, infrastructure, presentation).
• You need timing and performance traces for Use Cases and database ops.
• You want user-aware error reports for server actions and procedures.
• You need consistent exception severity mapping and contextual tags.
• You want breadcrumbs to follow user flow and authentication events.

Best practices

• Set Sentry user context once in the authenticated procedure, not in each action.
• Wrap Use Case.execute with a transaction span and add child spans for domain and repository work.
• Tag errors by layer and include minimal context objects (avoid sensitive fields).
• Map domain exception types to severity levels: validation=warning, not_found=info, business=error.
• Add breadcrumbs for auth, validation, and key processing steps to reconstruct flow.

Example use cases

• Trace execution time of a CreateCategory Use Case and surface slow repository writes.
• Capture a ValidationException with tags and input context when entity creation fails.
• Set user context during authentication so server action errors include user id and email.
• Record DB operation spans for CategoryRepository.save and CategoryRepository.findById to monitor latency.
• Report client-side action errors from an ErrorBoundary with component tags and automatic capture.