When should I use logIssue vs logError?

Use logIssue for unexpected system failures that require immediate investigation in Sentry. Use logError for error conditions that need to be in the logs but do not require an alert or Sentry issue.

What is the core principle of this logging skill?

The core principle is to prevent noise: 4xx user-correctable errors must never create Sentry issues, while 5xx system failures must always generate an issue for investigation.

Does this skill allow the use of standard console.log?

No, it flags raw console methods as anti-patterns. It enforces the use of structured logging wrappers like logDebug, logInfo, and logIssue to maintain consistent context.

How does it help with debugging production issues?

It ensures all system errors are logged with structured context (loggerScope, contexts, extra) and checks that Event IDs are provided to users for reference in support tickets.

Logging & Observability Reviewer

Name: Logging & Observability Reviewer
Author: getsentry

bygetsentry

•

575

•

分析と監視

Enforces standardized error handling and logging patterns to ensure system failures are tracked while reducing noise from user errors.

This skill helps developers maintain a clean and actionable observability stack by enforcing strict logging hierarchies within the Sentry MCP codebase. It automatically identifies common anti-patterns, such as logging user-correctable 4xx errors to Sentry or missing critical 5xx system failure alerts. By guiding the use of specialized functions like logIssue, logWarn, and logError, it ensures that every reported incident is meaningful, contains the necessary structured context for rapid debugging, and adheres to the project's architectural standards.

主な機能

01575 GitHub stars

02Detection of raw console methods and direct Sentry SDK bypasses

03Verification of structured context including loggerScope and extra metadata

04Guidance for returning Event IDs in user-facing system error messages

05Enforcement of the 4xx/5xx error logging hierarchy

06Validation of specialized error wrappers like agentTool

ユースケース

01Auditing existing tool handlers for missing observability in critical failure paths

02Automating code reviews to prevent Sentry noise caused by user validation failures

03Standardizing error discrimination and logging across complex MCP server implementations

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add getsentry/sentry-mcp logging-observability

For use in Claude.ai and ChatGPT

Download Skill