# Build Reliable Error Tracking and Monitoring

Production errors are difficult to diagnose when telemetry and alerts are inconsistent. This skill designs practical monitoring, logging, grouping, recovery, and dashboard workflows.

## Install

```bash
npx skillstore add sickn33/error-debugging-error-trace
```

## Metadata

- Status: approved
- Slug: sickn33-error-debugging-error-trace
- Skillstore revision: r2
- Version status: missing
- Tree hash: e19780d53ee4c7ba2e2701dc41d121d37af6244e64c9fd4ba3571677b75b8d9e
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/error-debugging-error-trace
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/sickn33-error-debugging-error-trace
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-error-debugging-error-trace/manifest

## Capabilities

- Assesses codebases for exception handling, logging frameworks, and monitoring gaps.
- Designs Sentry and custom error tracking integrations with sampling and redaction.
- Creates structured logging patterns for console, file, and Elasticsearch transports.
- Defines alert thresholds, cooldowns, routing channels, and triage workflows.
- Builds error grouping, fingerprinting, deduplication, retry, and circuit breaker strategies.
- Outlines performance monitoring and real-time error dashboard components.

## Use Cases

- Improve Service Error Capture: Assess exception handling and add structured, privacy-aware error reporting to a service.
- Reduce Alert Noise: Design severity thresholds, cooldowns, alert channels, and triage workflows for production incidents.
- Standardize Observability: Create shared grouping, performance, recovery, and dashboard patterns for multiple services.

## Prompt Templates

### Assess Error Monitoring

```
Review this service structure and current error handling. Identify monitoring gaps, privacy risks, and the three highest priority improvements.
```

### Design Structured Logging

```
Design structured logging for this application. Define fields, levels, redaction rules, retention needs, and transports for development and production.
```

### Create Alerting and Triage

```
Create alert rules for these service objectives and metrics. Include thresholds, windows, cooldowns, routing, ownership, and validation tests.
```

### Plan an Observability System

```
Design an end-to-end error monitoring system for this architecture. Cover capture, grouping, tracing, alerts, recovery, dashboards, privacy, rollout, and verification.
```

## Limitations

- The examples require adaptation to each runtime, framework, and monitoring provider.
- The skill cannot inspect deployed systems without approved runtime and monitoring access.
- Several examples are reference patterns and require dependency, type, and production readiness checks.
- Generated redaction rules and alert thresholds require privacy and operational review.

## Best Practices

- Start with service objectives, failure modes, data sensitivity, and incident ownership.
- Redact sensitive fields before export and validate controls with representative test events.
- Tune grouping and alerts using production evidence, then document thresholds and runbooks.

## Anti Patterns

- Do not send request bodies, credentials, or personal data to telemetry by default.
- Do not page on every exception without thresholds, grouping, and cooldowns.
- Do not deploy reference examples without dependency, privacy, load, and failure testing.

## Security Audit

- Audited at: 2026-07-23T23:39:22.726\+00:00
- Summary: All 15 static findings are false positives involving template literals, Markdown code spans, defensive redaction keys, and expected observability network examples. A medium privacy concern remains because examples can export user context or log identifiers and full URLs without complete redaction.

## Stats

- Views: 127
- Downloads: 10
- Favorites: 0
- Popularity score: 0