Official agent skill

Sentry Nestjs SDK

by getsentry in getsentry/sentry-for-ai

Full Sentry SDK setup for NestJS. An agent skill from getsentry/sentry-for-ai.

OfficialApache-2.0Auto-check passedBackend & APIs

Install Sentry Nestjs SDK

skills CLI
$ npx skills add getsentry/sentry-for-ai --skill sentry-nestjs-sdk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getsentry/sentry-for-ai sentry-nestjs-sdk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getsentry/sentry-for-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-legacy/sentry-nestjs-sdk .claude/skills/sentry-nestjs-sdk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sentry-nestjs-sdk
GitHub stars
268
Token cost
~8.7k tokens
SKILL.md length
1,823 words
Files
8 (incl. references)
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Full Sentry SDK setup for NestJS. An agent skill from getsentry/sentry-for-ai.

  • Works in 4 steps: Detect → Recommend → Guide → …
  • Asked to add Sentry to NestJS
  • SKILL.md covers Invoke This Skill When, Phase 1: Detect, Phase 2: Recommend and Phase 3: Guide, plus 4 more sections
  • Calls npm, node and npx; reaches docs.sentry.io; needs SENTRY_PROXY_TOKEN and SENTRY_AUTH_TOKEN

What it does

Sentry Nestjs SDK is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization. Full Sentry SDK setup for NestJS. Use when asked to "add Sentry to NestJS", "install @sentry/nestjs", "setup Sentry in NestJS", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for NestJS applications. Supports Express and Fastify adapters, GraphQL, microservices, WebSockets, and background jobs.

Its SKILL.md is about 8.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/ai-monitoring.md`, `references/crons.md` and `references/error-monitoring.md`).

It sits in Backend & APIs, covering Microservices, Background jobs and Scheduled and recurring tasks. It works with Sentry, NestJS, Fastify and GraphQL. The repository describes itself as: Teach your AI coding assistant how to use Sentry - setup, debugging, alerts, and more. The licence is Apache-2.0.

When your agent uses it

  • Asked to add Sentry to NestJS
  • Install @sentry/nestjs
  • Setup Sentry in NestJS
  • Configure error monitoring

Example prompts

  • “add Sentry to NestJS”
  • “install @sentry/nestjs”
  • “setup Sentry in NestJS”
  • “/sentry-nestjs-sdk”

Requirements

  • Node.js
  • A credential in SENTRY_PROXY_TOKEN

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Detect
  2. Recommend
  3. Guide
  4. Cross-Link

What it can do on your machine

Read from SKILL.md and the folder at commit d8fd106. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • node
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • docs.sentry.io

    Also links to:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SENTRY_PROXY_TOKEN
    • SENTRY_AUTH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sentry Nestjs SDK loads about 8.7k tokens when it runs, and up to ~32k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 1,823 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~8.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~32k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from getsentry/sentry-for-ai at commit d8fd106, republished under its Apache-2.0 licence (© getsentry). 1,823 words, ~8,744 tokens.

Download SKILL.mdSave it as .claude/skills/sentry-nestjs-sdk/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
sentry-nestjs-sdk
description
Full Sentry SDK setup for NestJS. Use when asked to "add Sentry to NestJS", "install @sentry/nestjs", "setup Sentry in NestJS", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for NestJS applications. Supports Express and Fastify adapters, GraphQL, microservices, WebSockets, and background jobs.
license
Apache-2.0
category
sdk-setup
parent
sentry-sdk-setup
disable-model-invocation
true

All Skills > SDK Setup > NestJS SDK

Sentry NestJS SDK

Opinionated wizard that scans your NestJS project and guides you through complete Sentry setup.

Invoke This Skill When

  • User asks to "add Sentry to NestJS" or "setup Sentry" in a NestJS app
  • User wants error monitoring, tracing, profiling, logging, metrics, or crons in NestJS
  • User mentions @sentry/nestjs or Sentry + NestJS
  • User wants to monitor NestJS controllers, services, guards, microservices, or background jobs

Note: SDK versions and APIs below reflect @sentry/nestjs 10.x (NestJS 8–11 supported). Always verify against docs.sentry.io/platforms/node/guides/nestjs/ before implementing.


Phase 1: Detect

Run these commands to understand the project before making recommendations:

bash
# Confirm NestJS project
grep -E '"@nestjs/core"' package.json 2>/dev/null

# Check NestJS version
node -e "console.log(require('./node_modules/@nestjs/core/package.json').version)" 2>/dev/null

# Check existing Sentry
grep -i sentry package.json 2>/dev/null
ls src/instrument.ts 2>/dev/null
grep -r "Sentry.init\|@sentry" src/main.ts src/instrument.ts 2>/dev/null

# Check for existing Sentry DI wrapper (common in enterprise NestJS)
grep -rE "SENTRY.*TOKEN|SentryProxy|SentryService" src/ libs/ 2>/dev/null

# Check for config-class-based init (vs env-var-based)
grep -rE "class SentryConfig|SentryConfig" src/ libs/ 2>/dev/null

# Check if SentryModule.forRoot() is already registered in a shared module
grep -rE "SentryModule\.forRoot|SentryProxyModule" src/ libs/ 2>/dev/null

# Detect HTTP adapter (default is Express)
grep -E "FastifyAdapter|@nestjs/platform-fastify" package.json src/main.ts 2>/dev/null

# Detect GraphQL
grep -E '"@nestjs/graphql"|"apollo-server"' package.json 2>/dev/null

# Detect microservices
grep '"@nestjs/microservices"' package.json 2>/dev/null

# Detect WebSockets
grep -E '"@nestjs/websockets"|"socket.io"' package.json 2>/dev/null

# Detect task queues / scheduled jobs
grep -E '"@nestjs/bull"|"@nestjs/bullmq"|"@nestjs/schedule"|"bullmq"|"bull"' package.json 2>/dev/null

# Detect databases
grep -E '"@prisma/client"|"typeorm"|"mongoose"|"pg"|"mysql2"' package.json 2>/dev/null

# Detect AI libraries
grep -E '"openai"|"@anthropic-ai"|"langchain"|"@langchain"|"@google/generative-ai"|"ai"' package.json 2>/dev/null

# Check for companion frontend
ls -d ../frontend ../web ../client ../ui 2>/dev/null

What to note:

  • Is @sentry/nestjs already installed? If yes, check if instrument.ts exists and Sentry.init() is called — may just need feature config.
  • Sentry DI wrapper detected? → The project wraps Sentry behind a DI token (e.g. SENTRY_PROXY_TOKEN) for testability. Use the injected proxy for all runtime Sentry calls (startSpan, captureException, withIsolationScope) instead of importing @sentry/nestjs directly in controllers, services, and processors. Only instrument.ts should import @sentry/nestjs directly.
  • Config class detected? → The project uses a typed config class for Sentry.init() options (e.g. loaded from YAML or @nestjs/config). Any new SDK options must be added to the config type — do not hardcode values that should be configurable per environment.
  • SentryModule.forRoot() already registered? → If it's in a shared module (e.g. a Sentry proxy module), do not add it again in AppModule — this causes duplicate interceptor registration.
  • Express (default) or Fastify adapter? Express is fully supported; Fastify works but has known edge cases.
  • GraphQL detected? → SentryGlobalFilter handles it natively.
  • Microservices detected? → Recommend RPC exception filter.
  • Task queues / @nestjs/schedule? → Recommend crons.
  • AI libraries? → Auto-instrumented, zero config.
  • Prisma? → Requires manual prismaIntegration().
  • Companion frontend? → Triggers Phase 4 cross-link.

Phase 2: Recommend

Based on what you found, present a concrete proposal. Don't ask open-ended questions — lead with a recommendation:

Always recommended (core coverage):

  • ✅ Error Monitoring — captures unhandled exceptions across HTTP, GraphQL, RPC, and WebSocket contexts
  • ✅ Tracing — auto-instruments middleware, guards, pipes, interceptors, filters, and route handlers

Recommend when detected:

  • ✅ Profiling — production apps where CPU performance matters (@sentry/profiling-node)
  • ✅ Logging — structured Sentry Logs + optional console capture
  • ✅ Crons — @nestjs/schedule, Bull, or BullMQ detected
  • ✅ Metrics — business KPIs or SLO tracking
  • ✅ AI Monitoring — OpenAI/Anthropic/LangChain/etc. detected (auto-instrumented, zero config)

Recommendation matrix:

FeatureRecommend when...Reference
Error MonitoringAlways — non-negotiable baseline${SKILL_ROOT}/references/error-monitoring.md
TracingAlways — NestJS lifecycle is auto-instrumented${SKILL_ROOT}/references/tracing.md
ProfilingProduction + CPU-sensitive workloads${SKILL_ROOT}/references/profiling.md
LoggingAlways; enhanced for structured log aggregation${SKILL_ROOT}/references/logging.md
MetricsCustom business KPIs or SLO tracking${SKILL_ROOT}/references/metrics.md
Crons@nestjs/schedule, Bull, or BullMQ detected${SKILL_ROOT}/references/crons.md
AI MonitoringOpenAI/Anthropic/LangChain/etc. detected${SKILL_ROOT}/references/ai-monitoring.md

Propose: "I recommend Error Monitoring + Tracing + Logging. Want Profiling, Crons, or AI Monitoring too?"


Phase 3: Guide

Install
bash
# Core SDK (always required — includes @sentry/node)
npm install @sentry/nestjs

# With profiling support (optional)
npm install @sentry/nestjs @sentry/profiling-node

⚠️ Do NOT install @sentry/node alongside @sentry/nestjs — @sentry/nestjs re-exports everything from @sentry/node. Installing both causes duplicate registration.

Three-File Setup (Required)

NestJS requires a specific three-file initialization pattern because the Sentry SDK must patch Node.js modules (via OpenTelemetry) before NestJS loads them.

Before creating new files, check Phase 1 results:

  • If instrument.ts already exists → modify it, don't create a new one.
  • If a config class drives Sentry.init() → read options from the config instead of hardcoding env vars.
  • If a Sentry DI wrapper exists → use it for runtime calls instead of importing @sentry/nestjs directly in services/controllers.
Step 1: Create src/instrument.ts
typescript
import * as Sentry from "@sentry/nestjs";
// Optional: add profiling
// import { nodeProfilingIntegration } from "@sentry/profiling-node";

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  environment: process.env.SENTRY_ENVIRONMENT ?? "production",
  release: process.env.SENTRY_RELEASE,

  // Data collection (SDK ≥ 10.57.0 — replaces deprecated sendDefaultPii)
  dataCollection: {
    // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
    // https://docs.sentry.io/platforms/javascript/guides/nestjs/configuration/options/#dataCollection
    // userInfo: false,
    // httpBodies: [],
  },

  // Tracing — lower to 0.1–0.2 in high-traffic production
  tracesSampleRate: 1.0,

  // Profiling (requires @sentry/profiling-node)
  // integrations: [nodeProfilingIntegration()],
  // profileSessionSampleRate: 1.0,
  // profileLifecycle: "trace",

  // Structured logs (SDK ≥ 9.41.0)
  enableLogs: true,
});

Config-driven Sentry.init(): If Phase 1 found a typed config class (e.g. SentryConfig), read options from it instead of using raw process.env. This is common in NestJS apps that use @nestjs/config or custom config loaders:

typescript
import * as Sentry from "@sentry/nestjs";
import { loadConfiguration } from "./config";

const config = loadConfiguration();

Sentry.init({
  dsn: config.sentry.dsn,
  environment: config.sentry.environment ?? "production",
  release: config.sentry.release,
  dataCollection: config.sentry.dataCollection ?? {
    // To disable sending user data and HTTP bodies, uncomment the lines below. For more info visit:
    // https://docs.sentry.io/platforms/javascript/guides/nestjs/configuration/options/#dataCollection
    // userInfo: false,
    // httpBodies: [],
  },
  tracesSampleRate: config.sentry.tracesSampleRate ?? 1.0,
  profileSessionSampleRate: config.sentry.profilesSampleRate ?? 1.0,
  profileLifecycle: "trace",
  enableLogs: true,
});

When adding new SDK options (e.g. dataCollection, profileSessionSampleRate), add them to the config type so they can be configured per environment.

Step 2: Import instrument.ts FIRST in src/main.ts
typescript
// instrument.ts MUST be the very first import — before NestJS or any other module
import "./instrument";

import { NestFactory } from "@nestjs/core";
import { AppModule } from "./app.module";

async function bootstrap() {
  const app = await NestFactory.create(AppModule);

  // Enable graceful shutdown — flushes Sentry events on SIGTERM/SIGINT
  app.enableShutdownHooks();

  await app.listen(3000);
}
bootstrap();

Why first? OpenTelemetry must monkey-patch http, express, database drivers, and other modules before they load. Any module that loads before instrument.ts will not be auto-instrumented.

Step 3: Register SentryModule and SentryGlobalFilter in src/app.module.ts
typescript
import { Module } from "@nestjs/common";
import { APP_FILTER } from "@nestjs/core";
import { SentryModule, SentryGlobalFilter } from "@sentry/nestjs/setup";
import { AppController } from "./app.controller";
import { AppService } from "./app.service";

@Module({
  imports: [
    SentryModule.forRoot(), // Registers SentryTracingInterceptor globally
  ],
  controllers: [AppController],
  providers: [
    AppService,
    {
      provide: APP_FILTER,
      useClass: SentryGlobalFilter, // Captures all unhandled exceptions
    },
  ],
})
export class AppModule {}

What each piece does:

  • SentryModule.forRoot() — registers SentryTracingInterceptor as a global APP_INTERCEPTOR, enabling HTTP transaction naming
  • SentryGlobalFilter — extends BaseExceptionFilter; captures exceptions across HTTP, GraphQL (rethrows HttpException without reporting), and RPC contexts

⚠️ Do NOT register SentryModule.forRoot() twice. If Phase 1 found it already imported in a shared library module (e.g. a SentryProxyModule or AnalyticsModule), do not add it again in AppModule. Duplicate registration causes every span to be intercepted twice, bloating trace data.

⚠️ Two entrypoints, different imports:

  • @sentry/nestjs → SDK init, capture APIs, decorators (SentryTraced, SentryCron, SentryExceptionCaptured)
  • @sentry/nestjs/setup → NestJS DI constructs (SentryModule, SentryGlobalFilter)

Never import SentryModule from @sentry/nestjs (main entrypoint) — it loads @nestjs/common before OpenTelemetry patches it, breaking auto-instrumentation.

ESM Setup (Node ≥ 18.19.0)

For ESM applications, use --import instead of a file import:

javascript
// instrument.mjs
import * as Sentry from "@sentry/nestjs";

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  tracesSampleRate: 1.0,
});
json
// package.json
{
  "scripts": {
    "start": "node --import ./instrument.mjs -r ts-node/register src/main.ts"
  }
}

Or via environment:

bash
NODE_OPTIONS="--import ./instrument.mjs" npm run start
Exception Filter Options

Choose the approach that fits your existing architecture:

Option A: No existing global filter — use SentryGlobalFilter (recommended)

Already covered in Step 3 above. This is the simplest option.

Option B: Existing custom global filter — add @SentryExceptionCaptured() decorator
typescript
import { Catch, ExceptionFilter, ArgumentsHost } from "@nestjs/common";
import { SentryExceptionCaptured } from "@sentry/nestjs";

@Catch()
export class YourExistingFilter implements ExceptionFilter {
  @SentryExceptionCaptured() // Wraps catch() to auto-report exceptions
  catch(exception: unknown, host: ArgumentsHost): void {
    // Your existing error handling continues unchanged
  }
}
Option C: Specific exception type — manual capture
typescript
import { ArgumentsHost, Catch } from "@nestjs/common";
import { BaseExceptionFilter } from "@nestjs/core";
import * as Sentry from "@sentry/nestjs";

@Catch(ExampleException)
export class ExampleExceptionFilter extends BaseExceptionFilter {
  catch(exception: ExampleException, host: ArgumentsHost) {
    Sentry.captureException(exception);
    super.catch(exception, host);
  }
}
Option D: Microservice RPC exceptions
typescript
import { Catch, RpcExceptionFilter, ArgumentsHost } from "@nestjs/common";
import { Observable, throwError } from "rxjs";
import { RpcException } from "@nestjs/microservices";
import * as Sentry from "@sentry/nestjs";

@Catch(RpcException)
export class SentryRpcFilter implements RpcExceptionFilter<RpcException> {
  catch(exception: RpcException, host: ArgumentsHost): Observable<any> {
    Sentry.captureException(exception);
    return throwError(() => exception.getError());
  }
}
Decorators
@SentryTraced(op?) — Instrument any method
typescript
import { Injectable } from "@nestjs/common";
import { SentryTraced } from "@sentry/nestjs";

@Injectable()
export class OrderService {
  @SentryTraced("order.process")
  async processOrder(orderId: string): Promise<void> {
    // Automatically wrapped in a Sentry span
  }

  @SentryTraced()  // Defaults to op: "function"
  async fetchInventory() { ... }
}
@SentryCron(slug, config?) — Monitor scheduled jobs
typescript
import { Injectable } from "@nestjs/common";
import { Cron } from "@nestjs/schedule";
import { SentryCron } from "@sentry/nestjs";

@Injectable()
export class ReportService {
  @Cron("0 * * * *")
  @SentryCron("hourly-report", {
    // @SentryCron must come AFTER @Cron
    schedule: { type: "crontab", value: "0 * * * *" },
    checkinMargin: 2, // Minutes before marking missed
    maxRuntime: 10, // Max runtime in minutes
    timezone: "UTC",
  })
  async generateReport() {
    // Check-in sent automatically on start/success/failure
  }
}
Background Job Scope Isolation

Background jobs share the default isolation scope — wrap with Sentry.withIsolationScope() to prevent cross-contamination:

typescript
import * as Sentry from "@sentry/nestjs";
import { Injectable } from "@nestjs/common";
import { Cron, CronExpression } from "@nestjs/schedule";

@Injectable()
export class JobService {
  @Cron(CronExpression.EVERY_HOUR)
  handleCron() {
    Sentry.withIsolationScope(() => {
      Sentry.setTag("job", "hourly-sync");
      this.doWork();
    });
  }
}

Apply withIsolationScope to: @Cron(), @Interval(), @OnEvent(), @Processor(), and any code outside the request lifecycle.

Working with Sentry DI Wrappers

Some NestJS projects wrap Sentry behind a dependency injection token (e.g. SENTRY_PROXY_TOKEN) for testability and decoupling. If Phase 1 detected this pattern, use the injected service for all runtime Sentry calls — do not import @sentry/nestjs directly in controllers, services, or processors.

typescript
import { Controller, Inject } from "@nestjs/common";
import { SENTRY_PROXY_TOKEN, type SentryProxyService } from "./sentry-proxy";

@Controller("orders")
export class OrderController {
  constructor(
    @Inject(SENTRY_PROXY_TOKEN) private readonly sentry: SentryProxyService,
    private readonly orderService: OrderService,
  ) {}

  @Post()
  async createOrder(@Body() dto: CreateOrderDto) {
    return this.sentry.startSpan(
      { name: "createOrder", op: "http" },
      async () => this.orderService.create(dto),
    );
  }
}

Where direct @sentry/nestjs import is still correct:

  • instrument.ts — always uses import * as Sentry from "@sentry/nestjs" for Sentry.init()
  • Standalone scripts and exception filters that run outside the DI container
Verification

Add a test endpoint to confirm events reach Sentry:

typescript
import { Controller, Get } from "@nestjs/common";
import * as Sentry from "@sentry/nestjs";

@Controller()
export class DebugController {
  @Get("/debug-sentry")
  triggerError() {
    throw new Error("My first Sentry error from NestJS!");
  }

  @Get("/debug-sentry-span")
  triggerSpan() {
    return Sentry.startSpan({ op: "test", name: "NestJS Test Span" }, () => {
      return { status: "span created" };
    });
  }
}

Hit GET /debug-sentry and check the Sentry Issues dashboard within seconds.

For Each Agreed Feature

Walk through features one at a time. Load the reference, follow its steps, verify before moving on:

FeatureReference fileLoad when...
Error Monitoring${SKILL_ROOT}/references/error-monitoring.mdAlways (baseline)
Tracing${SKILL_ROOT}/references/tracing.mdAlways (NestJS routes are auto-traced)
Profiling${SKILL_ROOT}/references/profiling.mdCPU-intensive production apps
Logging${SKILL_ROOT}/references/logging.mdStructured log aggregation needed
Metrics${SKILL_ROOT}/references/metrics.mdCustom KPIs / SLO tracking
Crons${SKILL_ROOT}/references/crons.mdScheduled jobs or task queues
AI Monitoring${SKILL_ROOT}/references/ai-monitoring.mdOpenAI/Anthropic/LangChain detected

For each feature: Read ${SKILL_ROOT}/references/<feature>.md, follow steps exactly, verify it works.


Configuration Reference

Show full SKILL.md (805 more words)Show less
Key Sentry.init() Options
OptionTypeDefaultPurpose
dsnstring—SDK disabled if empty; env: SENTRY_DSN
environmentstring"production"e.g., "staging"; env: SENTRY_ENVIRONMENT
releasestring—e.g., "myapp@1.0.0"; env: SENTRY_RELEASE
dataCollectionobjectSee belowControls what data the SDK collects (SDK ≥ 10.57.0)
dataCollection.userInfobooleantrueInclude IP addresses and user context
dataCollection.httpHeadersobjectSee belowCapture HTTP headers for requests/responses
dataCollection.cookiesboolean|objecttrueCapture cookies; use {allow: [...]} or {deny: [...]} for filtering
dataCollection.queryParamsboolean|objecttrueCapture URL query parameters; use {allow: [...]} or {deny: [...]} for filtering
dataCollection.genAIobjectSee belowControl AI input/output recording
sendDefaultPiibooleanfalseDeprecated — use dataCollection.userInfo instead
tracesSampleRatenumber—Transaction sample rate; undefined disables tracing
tracesSamplerfunction—Custom per-transaction sampling (overrides rate)
tracePropagationTargetsArray<string|RegExp>—URLs to propagate sentry-trace/baggage headers to
profileSessionSampleRatenumber—Continuous profiling session rate (SDK ≥ 10.27.0)
profileLifecycle"trace"|"manual""trace""trace" = auto-start profiler with spans; "manual" = call startProfiler()/stopProfiler()
enableLogsbooleanfalseSend structured logs to Sentry (SDK ≥ 9.41.0)
ignoreErrorsArray<string|RegExp>[]Error message patterns to suppress
ignoreTransactionsArray<string|RegExp>[]Transaction name patterns to suppress
beforeSendfunction—Hook to mutate or drop error events
beforeSendTransactionfunction—Hook to mutate or drop transaction events
beforeSendLogfunction—Hook to mutate or drop log events
debugbooleanfalseVerbose SDK debug output
maxBreadcrumbsnumber100Max breadcrumbs per event

dataCollection defaults:

  • httpHeaders: { request: true, response: true }
  • httpBodies: ["incomingRequest", "outgoingRequest", "incomingResponse", "outgoingResponse"]
  • userInfo: true
  • genAI: { inputs: true, outputs: true }
Environment Variables
VariableMaps toNotes
SENTRY_DSNdsnUsed if dsn not passed to init()
SENTRY_RELEASEreleaseAlso auto-detected from git SHA, Heroku, CircleCI
SENTRY_ENVIRONMENTenvironmentFalls back to "production"
SENTRY_AUTH_TOKENCLI/source mapsFor npx @sentry/wizard@latest -i sourcemaps
SENTRY_ORGCLI/source mapsOrganization slug
SENTRY_PROJECTCLI/source mapsProject slug
Auto-Enabled Integrations

These integrations activate automatically when their packages are detected — no integrations: [...] needed:

Auto-enabledNotes
httpIntegrationOutgoing HTTP calls via http/https/fetch
expressIntegrationExpress adapter (default NestJS)
nestIntegrationNestJS lifecycle (middleware, guards, pipes, interceptors, handlers)
onUncaughtExceptionIntegrationUncaught exceptions
onUnhandledRejectionIntegrationUnhandled promise rejections
openAIIntegrationOpenAI SDK (when installed)
anthropicAIIntegrationAnthropic SDK (when installed)
langchainIntegrationLangChain (when installed)
graphqlIntegrationGraphQL (when graphql package present)
postgresIntegrationpg driver
mysqlIntegrationmysql / mysql2
mongoIntegrationMongoDB / Mongoose
redisIntegrationioredis / redis
Integrations Requiring Manual Setup
IntegrationWhen to addCode
nodeProfilingIntegrationProfiling desiredimport { nodeProfilingIntegration } from "@sentry/profiling-node"
prismaIntegrationPrisma ORM usedintegrations: [Sentry.prismaIntegration()]
consoleLoggingIntegrationCapture console outputintegrations: [Sentry.consoleLoggingIntegration()]
localVariablesIntegrationCapture local var values in errorsintegrations: [Sentry.localVariablesIntegration()]

Verification

Test that Sentry is receiving events:

typescript
// Add a test endpoint (remove before production)
@Get("/debug-sentry")
getError() {
  throw new Error("My first Sentry error!");
}

Or send a test message without crashing:

typescript
import * as Sentry from "@sentry/nestjs";
Sentry.captureMessage("NestJS Sentry SDK test");

If nothing appears:

  1. Set debug: true in Sentry.init() — prints SDK internals to stdout
  2. Verify SENTRY_DSN env var is set in the running process
  3. Check that import "./instrument" is the first line in main.ts
  4. Confirm SentryModule.forRoot() is imported in AppModule
  5. Check DSN format: https://<key>@o<org>.ingest.sentry.io/<project>

After completing NestJS setup, check for a companion frontend missing Sentry:

bash
ls -d ../frontend ../web ../client ../ui 2>/dev/null
cat ../frontend/package.json ../web/package.json 2>/dev/null \
  | grep -E '"react"|"svelte"|"vue"|"next"|"nuxt"'

If a frontend exists without Sentry, suggest the matching skill:

Frontend detectedSuggest skill
Next.jssentry-nextjs-sdk
Reactsentry-react-sdk
Svelte / SvelteKitsentry-svelte-sdk
Vue / NuxtUse @sentry/vue — see docs.sentry.io/platforms/javascript/guides/vue/
React Native / Exposentry-react-native-sdk

Troubleshooting

IssueSolution
Events not appearingSet debug: true, verify SENTRY_DSN, check instrument.ts is imported first
Malformed DSN errorFormat: https://<key>@o<org>.ingest.sentry.io/<project>
Exceptions not capturedEnsure SentryGlobalFilter is registered via APP_FILTER in AppModule
Auto-instrumentation not workinginstrument.ts must be the first import in main.ts — before all NestJS imports
Profiling not startingRequires tracesSampleRate > 0 + profileSessionSampleRate > 0 + @sentry/profiling-node installed
enableLogs not workingRequires SDK ≥ 9.41.0
No traces appearingVerify tracesSampleRate is set (not undefined)
Too many transactionsLower tracesSampleRate or use tracesSampler to drop health checks
Fastify + GraphQL issuesKnown edge cases — see GitHub #13388; prefer Express for GraphQL
Background job events mixedWrap job body in Sentry.withIsolationScope(() => { ... })
Prisma spans missingAdd integrations: [Sentry.prismaIntegration()] to Sentry.init()
ESM syntax errorsSet registerEsmLoaderHooks: false (disables ESM hooks; also disables auto-instrumentation for ESM modules)
SentryModule breaks instrumentationMust import from @sentry/nestjs/setup, never from @sentry/nestjs
RPC exceptions not capturedAdd dedicated SentryRpcExceptionFilter (see Option D in exception filter section)
WebSocket exceptions not capturedUse @SentryExceptionCaptured() on gateway handleConnection/handleDisconnect
@SentryCron not triggeringDecorator order matters — @SentryCron MUST come after @Cron
TypeScript path alias issuesEnsure tsconfig.json paths are configured so instrument resolves from main.ts location
import * as Sentry ESLint errorMany projects ban namespace imports. Use named imports (import { startSpan, captureException } from "@sentry/nestjs") or use the project's DI proxy instead
profilesSampleRate vs profileSessionSampleRateprofilesSampleRate is deprecated in SDK 10.x. Use profileSessionSampleRate + profileLifecycle: "trace" instead
Duplicate spans on every requestSentryModule.forRoot() registered in multiple modules. Ensure it's only called once — check shared/library modules
Config property not recognized in instrument.tsWhen using a typed config class, new SDK options must be added to the config type definition and the project rebuilt before TypeScript recognizes them
Version Requirements
FeatureMinimum SDK Version
@sentry/nestjs package8.0.0
@SentryTraced decorator8.15.0
@SentryCron decorator8.16.0
Event Emitter auto-instrumentation8.39.0
SentryGlobalFilter (unified)8.40.0
Sentry.logger API (enableLogs)9.41.0
profileSessionSampleRate10.27.0
Node.js requirement≥ 18
Node.js for ESM --import≥ 18.19.0
NestJS compatibility8.x – 11.x

© getsentry, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills-legacy/sentry-nestjs-sdk of getsentry/sentry-for-ai.

  • SKILL.md
  • references/ai-monitoring.md
  • references/crons.md
  • references/error-monitoring.md
  • references/logging.md
  • references/metrics.md
  • references/profiling.md
  • references/tracing.md

Open the folder on GitHubat commit d8fd106

Compare with similar skills

Sentry Nestjs SDK next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sentry Nestjs SDK compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sentry Nestjs SDK this skillgetsentry/sentry-for-ai268—~8.7kAutomated safety check: PassApache-2.0
Nodejs Backend Patternsever-works/ever-works15817 repos~4kAutomated safety check: PassAGPL-3.0
Senior Backendalirezarezvani/claude-skills28k1 repos~3.8kAutomated safety check: PassMIT
Nestjsgiuseppe-trisciuoglio/developer-kit355—~1.4kAutomated safety check: NotesMIT
Nestjs Features Performanceaiskillstore/marketplace430—~3.8kAutomated safety check: PassMIT
GraphQL ArchitectJeffallan/claude-skills12k1 repos~1.3kAutomated safety check: PassMIT

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 17 repos~4k tokens
    Backend & APIsAuto-check passed
  • Senior Backend

    alirezarezvani/claude-skills

    Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening.

    28k GitHub starsUsed in 1 repo~3.8k tokens
    Backend & APIsAuto-check passed
  • Nestjs

    giuseppe-trisciuoglio/developer-kit

    Provides comprehensive NestJS framework patterns with Drizzle ORM integration for building scalable server-side applications.

    355 GitHub stars~1.4k tokensUpdated 27 days ago
    Backend & APIsAuto-check: notes
  • Nestjs Features Performance

    aiskillstore/marketplace

    Selects and implements NestJS runtime features, error and API contracts, security, testing, DevOps, performance, and safe scale.

    430 GitHub stars~3.8k tokensUpdated today
    Backend & APIsAuto-check passed
  • GraphQL Architect

    Jeffallan/claude-skills

    Designs GraphQL schemas and Apollo Federation graphs, with DataLoader resolvers, subscriptions, query complexity limits and caching.

    12k GitHub starsUsed in 1 repo~1.3k tokens
    Backend & APIsAuto-check passed
  • Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

    58k GitHub stars~2.9k tokensUpdated today
    Backend & APIsAuto-check passed

More from getsentry/sentry-for-ai

All 32 skills in this repo
  • Sentry Elixir SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Elixir. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Sentry Go SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Go. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Sentry Nextjs SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Next.js. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • Sentry Php SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for PHP. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes
  • Sentry Python SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Python. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Sentry React Router Framework SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for React Router Framework mode. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.8k tokensUpdated today
    Auto-check: notes

Categories

Questions about Sentry Nestjs SDK

What does Sentry Nestjs SDK do?

Full Sentry SDK setup for NestJS. An agent skill from getsentry/sentry-for-ai. Sentry Nestjs SDK is an agent skill from getsentry/sentry-for-ai, published by the product's own GitHub organization. Full Sentry SDK setup for NestJS.

When should I use Sentry Nestjs SDK?

Sentry Nestjs SDK fits situations like: asked to add Sentry to NestJS; install @sentry/nestjs; setup Sentry in NestJS; configure error monitoring.

How do I install Sentry Nestjs SDK in Claude Code?

Run `npx skills add getsentry/sentry-for-ai --skill sentry-nestjs-sdk -a claude-code`. Or copy the skill folder (skills-legacy/sentry-nestjs-sdk in getsentry/sentry-for-ai) into .claude/skills/sentry-nestjs-sdk in your project. Claude Code loads it when a task matches its description.

How do I install Sentry Nestjs SDK in Codex?

Run `npx skills add getsentry/sentry-for-ai --skill sentry-nestjs-sdk -a codex`. Or copy the skill folder (skills-legacy/sentry-nestjs-sdk in getsentry/sentry-for-ai) into .agents/skills/sentry-nestjs-sdk in your project. Codex loads it when a task matches its description.

Can I use Sentry Nestjs SDK in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/sentry-for-ai --skill sentry-nestjs-sdk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-nestjs-sdk, .gemini/skills/sentry-nestjs-sdk, .github/skills/sentry-nestjs-sdk and .opencode/skills/sentry-nestjs-sdk in your project.

What does Sentry Nestjs SDK need to run?

Going by SKILL.md and its folder, Sentry Nestjs SDK needs the command-line tools its instructions call (npm, node and npx) and credentials named SENTRY_PROXY_TOKEN and SENTRY_AUTH_TOKEN. Our summary lists: Node.js; A credential in SENTRY_PROXY_TOKEN.

Does Sentry Nestjs SDK access the network?

SKILL.md names 2 domains. In commands or code: docs.sentry.io; the agent is likely to contact it when it follows the instructions. As links in the text: github.com. This is read from the text; nothing was executed.

Is Sentry Nestjs SDK safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sentry Nestjs SDK use?

Sentry Nestjs SDK is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sentry Nestjs SDK use?

About 8.7k tokens (SKILL.md is roughly 35k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 23k tokens, read only when the agent opens those files.

What are the alternatives to Sentry Nestjs SDK?

Skills that share tags, products or a category with Sentry Nestjs SDK: Nodejs Backend Patterns (ever-works/ever-works, 158 stars), Senior Backend (alirezarezvani/claude-skills, 28k stars), Nestjs (giuseppe-trisciuoglio/developer-kit, 355 stars) and Nestjs Features Performance (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sentry Nestjs SDK?

getsentry (a GitHub organization, an official publisher) maintains it in getsentry/sentry-for-ai, which has 268 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 7, 2026.

Source: getsentry/sentry-for-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.