sentry-setup-logging

getsentry/sentry-agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/getsentry/sentry-agent-skills --skill sentry-setup-logging
0 commentsdiscussion
summary

Configure Sentry's structured logging feature.

skill.md

Setup Sentry Logging

Configure Sentry's structured logging feature.

Invoke This Skill When

  • User asks to "setup Sentry logging" or "capture logs in Sentry"
  • User wants to integrate logging libraries (Pino, Winston, Loguru) with Sentry
  • User asks about Sentry.logger or sentry_sdk.logger

Important: The SDK versions, API names, and code samples below are examples. Always verify against docs.sentry.io before implementing, as APIs and minimum versions may have changed.

Quick Reference

Platform Min SDK Enable Flag Logger API
JavaScript 9.41.0+ enableLogs: true Sentry.logger.*
Python 2.35.0+ enable_logs=True sentry_sdk.logger.*
Ruby 5.24.0+ config.enable_logs = true Sentry.logger.*

JavaScript Setup

1. Verify SDK version

grep -E '"@sentry/(nextjs|react|node|browser)"' package.json

2. Enable in Sentry.init()

Sentry.init({
  dsn: "YOUR_DSN",
  enableLogs: true,
});

3. Console capture (optional)

integrations: [
  Sentry.consoleLoggingIntegration({ levels: ["warn", "error"] }),
],

4. Use structured logging

Sentry.logger.info("User logged in", { userId: "123" });
Sentry.logger.error("Payment failed", { orderId: "456", amount: 99.99 });

// Template literals (creates searchable attributes)
Sentry.logger.info(Sentry.logger.fmt`User ${userId} purchased ${productName}`);

Third-party integrations

Library Integration Min SDK
Consola Sentry.createConsolaReporter() 10.12.0+
Console capture Sentry.consoleLoggingIntegration() 10.13.0+

Python Setup

1. Verify SDK version

pip show sentry-sdk | grep Version

2. Enable in init()

sentry_sdk.init(
    dsn="YOUR_DSN",
    enable_logs=True,
)

3. Stdlib logging capture (optional)

from sentry_sdk.integrations.logging import LoggingIntegration
integrations=[LoggingIntegration(sentry_logs_level=logging.INFO)]

4. Use structured logging

from sentry_sdk import logger as sentry_logger

sentry_logger.info("User logged in: {user_id}", user_id="123")
sentry_logger.error("Payment failed", order_id="456", amount=99.99)

Loguru integration

from sentry_sdk.integrations.loguru import LoguruIntegration
integrations=[LoguruIntegration(sentry_logs_level=LoggingLevels.INFO.value)]

Ruby Setup

1. Verify SDK version

bundle show sentry-ruby

2. Enable in init

Sentry.init do |config|
  config.dsn = "YOUR_DSN"
  config.enable_logs = true
  config.enabled_patches << :logger  # Optional: capture stdlib Logger
end

3. Use structured logging

Sentry.logger.info("User logged in")
Sentry.logger.error("Payment failed. Order: %{order_id}", order_id: "456")

Log Filtering

JavaScript

beforeSendLog: (log) => log.level === "info" ? null : log,

Python

def before_send_log(log, hint):
    return None if log["severity_text"] == "info" else log

Verification

After enabling logs, emit a test log and check the Sentry Logs dashboard (Explore > Logs):

Sentry.logger.info("Sentry logging test");

Troubleshooting

Issue Solution
Logs not appearing Verify SDK version, check enableLogs/enable_logs is set
Too many logs Use beforeSendLog to filter, reduce captured levels
Console not captured Add consoleLoggingIntegration to integrations array
how to use sentry-setup-logging

How to use sentry-setup-logging on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add sentry-setup-logging
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/getsentry/sentry-agent-skills --skill sentry-setup-logging

The skills CLI fetches sentry-setup-logging from GitHub repository getsentry/sentry-agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/sentry-setup-logging

Reload or restart Cursor to activate sentry-setup-logging. Access the skill through slash commands (e.g., /sentry-setup-logging) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.527 reviews
  • Xiao White· Dec 8, 2024

    Useful defaults in sentry-setup-logging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ganesh Mohane· Dec 4, 2024

    sentry-setup-logging is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Mia Yang· Nov 27, 2024

    We added sentry-setup-logging from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sakshi Patil· Nov 23, 2024

    sentry-setup-logging fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Yash Thakker· Nov 3, 2024

    Keeps context tight: sentry-setup-logging is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Oct 22, 2024

    I recommend sentry-setup-logging for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kiara Diallo· Oct 18, 2024

    sentry-setup-logging reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Oct 14, 2024

    sentry-setup-logging has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Aanya Khan· Sep 25, 2024

    sentry-setup-logging has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Lucas Chen· Sep 5, 2024

    Useful defaults in sentry-setup-logging — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 27

1 / 3