All Skills > SDK Setup > Python SDK
Sentry Python SDK
Opinionated wizard that scans your Python project and guides you through complete Sentry setup.
Invoke This Skill When
- User asks to "add Sentry to Python" or "setup Sentry" in a Python app
- User wants error monitoring, tracing, profiling, logging, metrics, or crons in Python
- User mentions
sentry-sdk, sentry_sdk, or Sentry + any Python framework
- User wants to monitor Django views, Flask routes, FastAPI endpoints, Celery tasks, or scheduled jobs
Note: SDK versions and APIs below reflect Sentry docs at time of writing (sentry-sdk 2.x).
Always verify against docs.sentry.io/platforms/python/ before implementing.
Phase 1: Detect
Run these commands to understand the project before making recommendations:
# Check existing Sentry
grep -i sentry requirements.txt pyproject.toml setup.cfg setup.py 2>/dev/null
# Detect web framework
grep -rE "django|flask|fastapi|starlette|aiohttp|tornado|quart|falcon|sanic|bottle" \
requirements.txt pyproject.toml 2>/dev/null
# Detect task queues
grep -rE "celery|rq|huey|arq|dramatiq" requirements.txt pyproject.toml 2>/dev/null
# Detect logging libraries
grep -E "loguru" requirements.txt pyproject.toml 2>/dev/null
# Detect AI libraries
grep -rE "openai|anthropic|langchain|huggingface|google-genai|pydantic-ai|litellm" \
requirements.txt pyproject.toml 2>/dev/null
# Detect schedulers / crons
grep -rE "celery|apscheduler|schedule|crontab" requirements.txt pyproject.toml 2>/dev/null
# Check for companion frontend
ls frontend/ web/ client/ ui/ static/ templates/ 2>/dev/null
What to note:
- Is
sentry-sdk already in requirements? If yes, check if sentry_sdk.init() is present — may just need feature config.
- Which framework? (Determines where to place
sentry_sdk.init().)
- Which task queue? (Celery needs dual-process init; RQ needs a settings file.)
- AI libraries? (OpenAI, Anthropic, LangChain are auto-instrumented.)
- 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, supports
ExceptionGroup (Python 3.11+)
- ✅ Logging — Python
logging stdlib auto-captured; enhanced if Loguru detected
Recommend when detected:
- ✅ Tracing — HTTP framework detected (Django/Flask/FastAPI/etc.)
- ✅ AI Monitoring — OpenAI/Anthropic/LangChain/etc. detected (auto-instrumented, zero config)
- ⚡ Profiling — production apps where performance matters
- ⚡ Crons — Celery Beat, APScheduler, or cron patterns detected
- ⚡ Metrics — business KPIs, SLO tracking
Recommendation matrix:
| Feature |
Recommend when... |
Reference |
| Error Monitoring |
Always — non-negotiable baseline |
${SKILL_ROOT}/references/error-monitoring.md |
| Tracing |
Django/Flask/FastAPI/AIOHTTP/etc. detected |
${SKILL_ROOT}/references/tracing.md |
| Profiling |
Production + performance-sensitive workload |
${SKILL_ROOT}/references/profiling.md |
| Logging |
Always (stdlib); enhanced for Loguru |
${SKILL_ROOT}/references/logging.md |
| Metrics |
Business events or SLO tracking needed |
${SKILL_ROOT}/references/metrics.md |
| Crons |
Celery Beat, APScheduler, or cron patterns |
${SKILL_ROOT}/references/crons.md |
| AI Monitoring |
OpenAI/Anthropic/LangChain/etc. detected |
${SKILL_ROOT}/references/ai-monitoring.md |
Propose: "I recommend Error Monitoring + Tracing [+ Logging if applicable]. Want Profiling, Crons, or AI Monitoring too?"
Phase 3: Guide
Install
# Core SDK (always required)
pip install sentry-sdk
# Optional extras (install only what matches detected framework):
pip install "sentry-sdk[django]"
pip install "sentry-sdk[flask]"
pip install "sentry-sdk[fastapi]"
pip install "sentry-sdk[celery]"
pip install "sentry-sdk[aiohttp]"
pip install "sentry-sdk[tornado]"
# Multiple extras:
pip install "sentry-sdk[django,celery]"
Extras are optional — plain sentry-sdk works for all frameworks. Extras install complementary packages.
Quick Start — Recommended Init
Full init enabling the most features with sensible defaults. Place before any app/framework code:
import sentry_sdk
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
environment=os.environ.get("SENTRY_ENVIRONMENT", "production"),
release=os.environ.get("SENTRY_RELEASE"), # e.g. "myapp@1.0.0"
send_default_pii=True,
# Tracing (lower to 0.1–0.2 in high-traffic production)
traces_sample_rate=1.0,
# Profiling — continuous, tied to active spans
profile_session_sample_rate=1.0,
profile_lifecycle="trace",
# Structured logs (SDK ≥ 2.35.0)
enable_logs=True,
)
Where to Initialize Per Framework
| Framework |
Where to call sentry_sdk.init() |
Notes |
| Django |
Top of settings.py, before any imports |
No middleware needed — Sentry patches Django internally |
| Flask |
Before app = Flask(__name__) |
Must precede app creation |
| FastAPI |
Before app = FastAPI() |
StarletteIntegration + FastApiIntegration auto-enabled together |
| Starlette |
Before app = Starlette(...) |
Same auto-integration as FastAPI |
| AIOHTTP |
Module level, before web.Application() |
|
| Tornado |
Module level, before app setup |
No integration class needed |
| Quart |
Before app = Quart(__name__) |
|
| Falcon |
Module level, before app = falcon.App() |
|
| Sanic |
Inside @app.listener("before_server_start") |
Sanic's lifecycle requires async init |
| Celery |
@signals.celeryd_init.connect in worker AND in calling process |
Dual-process init required |
| RQ |
mysettings.py loaded by worker via rq worker -c mysettings |
|
| ARQ |
Both worker module and enqueuing process |
|
Django example (settings.py):
import sentry_sdk
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
send_default_pii=True,
traces_sample_rate=1.0,
profile_session_sample_rate=1.0,
profile_lifecycle="trace",
enable_logs=True,
)
# rest of Django settings...
INSTALLED_APPS = [...]
FastAPI example (main.py):
import sentry_sdk
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
send_default_pii=True,
traces_sample_rate=1.0,
profile_session_sample_rate=1.0,
profile_lifecycle="trace",
enable_logs=True,
)
from fastapi import FastAPI
app = FastAPI()
Auto-Enabled vs Explicit Integrations
Most integrations activate automatically when their package is installed — no integrations=[...] needed:
| Auto-enabled |
Explicit required |
| Django, Flask, FastAPI, Starlette, AIOHTTP, Tornado, Quart, Falcon, Sanic, Bottle |
DramatiqIntegration |
| Celery, RQ, Huey, ARQ |
GRPCIntegration |
| SQLAlchemy, Redis, asyncpg, pymongo |
StrawberryIntegration |
| Requests, HTTPX, aiohttp-client |
AsyncioIntegration |
| OpenAI, Anthropic, LangChain, Pydantic AI, MCP |
OpenTelemetryIntegration |
Python logging, Loguru |
WSGIIntegration / ASGIIntegration |
For Each Agreed Feature
Walk through features one at a time. Load the reference, follow its steps, verify before moving on:
| Feature |
Reference file |
Load when... |
| Error Monitoring |
${SKILL_ROOT}/references/error-monitoring.md |
Always (baseline) |
| Tracing |
${SKILL_ROOT}/references/tracing.md |
HTTP handlers / distributed tracing |
| Profiling |
${SKILL_ROOT}/references/profiling.md |
Performance-sensitive production |
| Logging |
${SKILL_ROOT}/references/logging.md |
Always; enhanced for Loguru |
| Metrics |
${SKILL_ROOT}/references/metrics.md |
Business KPIs / SLO tracking |
| Crons |
${SKILL_ROOT}/references/crons.md |
Scheduler / cron patterns detected |
| AI Monitoring |
${SKILL_ROOT}/references/ai-monitoring.md |
AI library detected |
For each feature: Read ${SKILL_ROOT}/references/<feature>.md, follow steps exactly, verify it works.
Configuration Reference
Key sentry_sdk.init() Options
| Option |
Type |
Default |
Purpose |
dsn |
str |
None |
SDK disabled if empty; env: SENTRY_DSN |
environment |
str |
"production" |
e.g., "staging"; env: SENTRY_ENVIRONMENT |
release |
str |
None |
e.g., "myapp@1.0.0"; env: SENTRY_RELEASE |
send_default_pii |
bool |
False |
Include IP, headers, cookies, auth user |
traces_sample_rate |
float |
None |
Transaction sample rate; None disables tracing |
traces_sampler |
Callable |
None |
Custom per-transaction sampling (overrides rate) |
profile_session_sample_rate |
float |
None |
Continuous profiling session rate |
profile_lifecycle |
str |
"manual" |
"trace" = auto-start profiler with spans |
profiles_sample_rate |
float |
None |
Transaction-based profiling rate |
enable_logs |
bool |
False |
Send logs to Sentry (SDK ≥ 2.35.0) |
sample_rate |
float |
1.0 |
Error event sample rate |
attach_stacktrace |
bool |
False |
Stack traces on capture_message() |
max_breadcrumbs |
int |
100 |
Max breadcrumbs per event |
debug |
bool |
False |
Verbose SDK debug output |
before_send |
Callable |
None |
Hook to mutate/drop error events |
before_send_transaction |
Callable |
None |
Hook to mutate/drop transaction events |
ignore_errors |
list |
[] |
Exception types or regex patterns to suppress |
auto_enabling_integrations |
bool |
True |
Set False to disable all auto-detection |
Environment Variables
| Variable |
Maps to |
Notes |
SENTRY_DSN |
dsn |
|
SENTRY_RELEASE |
release |
Also auto-detected from git SHA, Heroku, CircleCI, CodeBuild, GAE |
SENTRY_ENVIRONMENT |
environment |
|
SENTRY_DEBUG |
debug |
|
Verification
Test that Sentry is receiving events:
# Trigger a real error event — check dashboard within seconds
division_by_zero = 1 / 0
Or for a non-crashing check:
sentry_sdk.capture_message("Sentry Python SDK test")
If nothing appears:
- Set
debug=True in sentry_sdk.init() — prints SDK internals to stdout
- Verify the DSN is correct
- Check
SENTRY_DSN env var is set in the running process
- For Celery/RQ: ensure init runs in the worker process, not just the calling process
Phase 4: Cross-Link
After completing Python setup, check for a companion frontend missing Sentry:
ls frontend/ web/ client/ ui/ 2>/dev/null
cat frontend/package.json web/package.json client/package.json 2>/dev/null \
| grep -E '"react"|"svelte"|"vue"|"next"|"nuxt"'
If a frontend exists without Sentry, suggest the matching skill:
| Frontend detected |
Suggest skill |
| React / Next.js |
sentry-react-sdk |
| Svelte / SvelteKit |
sentry-svelte-sdk |
| Vue / Nuxt |
Use @sentry/vue — see docs.sentry.io/platforms/javascript/guides/vue/ |
| Other JS/TS |
sentry-react-sdk (covers generic browser JS patterns) |
Troubleshooting
| Issue |
Solution |
| Events not appearing |
Set debug=True, verify DSN, check env vars in the running process |
| Malformed DSN error |
Format: https://<key>@o<org>.ingest.sentry.io/<project> |
| Django exceptions not captured |
Ensure sentry_sdk.init() is at the top of settings.py before other imports |
| Flask exceptions not captured |
Init must happen before app = Flask(__name__) |
| FastAPI exceptions not captured |
Init before app = FastAPI(); both StarletteIntegration and FastApiIntegration auto-enabled |
| Celery task errors not captured |
Must call sentry_sdk.init() in the worker process via celeryd_init signal |
| Sanic init not working |
Init must be inside @app.listener("before_server_start"), not module level |
| uWSGI not capturing |
Add --enable-threads --py-call-uwsgi-fork-hooks to uWSGI command |
| No traces appearing |
Verify traces_sample_rate is set (not None); check that the integration is auto-enabled |
| Profiling not starting |
Requires traces_sample_rate > 0 + either profile_session_sample_rate or profiles_sample_rate |
enable_logs not working |
Requires SDK ≥ 2.35.0; for direct structured logs use sentry_sdk.logger; for stdlib bridging use LoggingIntegration(sentry_logs_level=...) |
| Too many transactions |
Lower traces_sample_rate or use traces_sampler to drop health checks |
| Cross-request data leaking |
Don't use get_global_scope() for per-request data — use get_isolation_scope() |
| RQ worker not reporting |
Pass --sentry-dsn="" to disable RQ's own Sentry shortcut; init via settings file instead |
1---2name: sentry-python-sdk3description: Full Sentry SDK setup for Python. Use when asked to "add Sentry to Python", "install sentry-sdk", "setup Sentry in Python", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for Python applications. Supports Django, Flask, FastAPI, Celery, Starlette, AIOHTTP, Tornado, and more.4license: Apache-2.05---67> [All Skills](../../SKILL_TREE.md) > [SDK Setup](../sentry-sdk-setup/SKILL.md) > Python SDK89# Sentry Python SDK1011Opinionated wizard that scans your Python project and guides you through complete Sentry setup.1213## Invoke This Skill When1415- User asks to "add Sentry to Python" or "setup Sentry" in a Python app16- User wants error monitoring, tracing, profiling, logging, metrics, or crons in Python17- User mentions `sentry-sdk`, `sentry_sdk`, or Sentry + any Python framework18- User wants to monitor Django views, Flask routes, FastAPI endpoints, Celery tasks, or scheduled jobs1920> **Note:** SDK versions and APIs below reflect Sentry docs at time of writing (sentry-sdk 2.x).21> Always verify against [docs.sentry.io/platforms/python/](https://docs.sentry.io/platforms/python/) before implementing.2223---2425## Phase 1: Detect2627Run these commands to understand the project before making recommendations:2829```bash30# Check existing Sentry31grep -i sentry requirements.txt pyproject.toml setup.cfg setup.py 2>/dev/null3233# Detect web framework34grep -rE "django|flask|fastapi|starlette|aiohttp|tornado|quart|falcon|sanic|bottle" \35 requirements.txt pyproject.toml 2>/dev/null3637# Detect task queues38grep -rE "celery|rq|huey|arq|dramatiq" requirements.txt pyproject.toml 2>/dev/null3940# Detect logging libraries41grep -E "loguru" requirements.txt pyproject.toml 2>/dev/null4243# Detect AI libraries44grep -rE "openai|anthropic|langchain|huggingface|google-genai|pydantic-ai|litellm" \45 requirements.txt pyproject.toml 2>/dev/null4647# Detect schedulers / crons48grep -rE "celery|apscheduler|schedule|crontab" requirements.txt pyproject.toml 2>/dev/null4950# Check for companion frontend51ls frontend/ web/ client/ ui/ static/ templates/ 2>/dev/null52```5354**What to note:**55- Is `sentry-sdk` already in requirements? If yes, check if `sentry_sdk.init()` is present — may just need feature config.56- Which framework? (Determines where to place `sentry_sdk.init()`.)57- Which task queue? (Celery needs dual-process init; RQ needs a settings file.)58- AI libraries? (OpenAI, Anthropic, LangChain are auto-instrumented.)59- Companion frontend? (Triggers Phase 4 cross-link.)6061---6263## Phase 2: Recommend6465Based on what you found, present a concrete proposal. Don't ask open-ended questions — lead with a recommendation:6667**Always recommended (core coverage):**68- ✅ **Error Monitoring** — captures unhandled exceptions, supports `ExceptionGroup` (Python 3.11+)69- ✅ **Logging** — Python `logging` stdlib auto-captured; enhanced if Loguru detected7071**Recommend when detected:**72- ✅ **Tracing** — HTTP framework detected (Django/Flask/FastAPI/etc.)73- ✅ **AI Monitoring** — OpenAI/Anthropic/LangChain/etc. detected (auto-instrumented, zero config)74- ⚡ **Profiling** — production apps where performance matters75- ⚡ **Crons** — Celery Beat, APScheduler, or cron patterns detected76- ⚡ **Metrics** — business KPIs, SLO tracking7778**Recommendation matrix:**7980| Feature | Recommend when... | Reference |81|---------|------------------|-----------|82| Error Monitoring | **Always** — non-negotiable baseline | `${SKILL_ROOT}/references/error-monitoring.md` |83| Tracing | Django/Flask/FastAPI/AIOHTTP/etc. detected | `${SKILL_ROOT}/references/tracing.md` |84| Profiling | Production + performance-sensitive workload | `${SKILL_ROOT}/references/profiling.md` |85| Logging | Always (stdlib); enhanced for Loguru | `${SKILL_ROOT}/references/logging.md` |86| Metrics | Business events or SLO tracking needed | `${SKILL_ROOT}/references/metrics.md` |87| Crons | Celery Beat, APScheduler, or cron patterns | `${SKILL_ROOT}/references/crons.md` |88| AI Monitoring | OpenAI/Anthropic/LangChain/etc. detected | `${SKILL_ROOT}/references/ai-monitoring.md` |8990Propose: *"I recommend Error Monitoring + Tracing [+ Logging if applicable]. Want Profiling, Crons, or AI Monitoring too?"*9192---9394## Phase 3: Guide9596### Install9798```bash99# Core SDK (always required)100pip install sentry-sdk101102# Optional extras (install only what matches detected framework):103pip install "sentry-sdk[django]"104pip install "sentry-sdk[flask]"105pip install "sentry-sdk[fastapi]"106pip install "sentry-sdk[celery]"107pip install "sentry-sdk[aiohttp]"108pip install "sentry-sdk[tornado]"109110# Multiple extras:111pip install "sentry-sdk[django,celery]"112```113114> Extras are optional — plain `sentry-sdk` works for all frameworks. Extras install complementary packages.115116### Quick Start — Recommended Init117118Full init enabling the most features with sensible defaults. Place **before** any app/framework code:119120```python121import sentry_sdk122123sentry_sdk.init(124 dsn=os.environ["SENTRY_DSN"],125 environment=os.environ.get("SENTRY_ENVIRONMENT", "production"),126 release=os.environ.get("SENTRY_RELEASE"), # e.g. "myapp@1.0.0"127 send_default_pii=True,128129 # Tracing (lower to 0.1–0.2 in high-traffic production)130 traces_sample_rate=1.0,131132 # Profiling — continuous, tied to active spans133 profile_session_sample_rate=1.0,134 profile_lifecycle="trace",135136 # Structured logs (SDK ≥ 2.35.0)137 enable_logs=True,138)139```140141### Where to Initialize Per Framework142143| Framework | Where to call `sentry_sdk.init()` | Notes |144|-----------|-----------------------------------|-------|145| **Django** | Top of `settings.py`, before any imports | No middleware needed — Sentry patches Django internally |146| **Flask** | Before `app = Flask(__name__)` | Must precede app creation |147| **FastAPI** | Before `app = FastAPI()` | `StarletteIntegration` + `FastApiIntegration` auto-enabled together |148| **Starlette** | Before `app = Starlette(...)` | Same auto-integration as FastAPI |149| **AIOHTTP** | Module level, before `web.Application()` | |150| **Tornado** | Module level, before app setup | No integration class needed |151| **Quart** | Before `app = Quart(__name__)` | |152| **Falcon** | Module level, before `app = falcon.App()` | |153| **Sanic** | Inside `@app.listener("before_server_start")` | Sanic's lifecycle requires async init |154| **Celery** | `@signals.celeryd_init.connect` in worker AND in calling process | Dual-process init required |155| **RQ** | `mysettings.py` loaded by worker via `rq worker -c mysettings` | |156| **ARQ** | Both worker module and enqueuing process | |157158**Django example** (`settings.py`):159```python160import sentry_sdk161162sentry_sdk.init(163 dsn=os.environ["SENTRY_DSN"],164 send_default_pii=True,165 traces_sample_rate=1.0,166 profile_session_sample_rate=1.0,167 profile_lifecycle="trace",168 enable_logs=True,169)170171# rest of Django settings...172INSTALLED_APPS = [...]173```174175**FastAPI example** (`main.py`):176```python177import sentry_sdk178179sentry_sdk.init(180 dsn=os.environ["SENTRY_DSN"],181 send_default_pii=True,182 traces_sample_rate=1.0,183 profile_session_sample_rate=1.0,184 profile_lifecycle="trace",185 enable_logs=True,186)187188from fastapi import FastAPI189app = FastAPI()190```191192### Auto-Enabled vs Explicit Integrations193194Most integrations activate automatically when their package is installed — no `integrations=[...]` needed:195196| Auto-enabled | Explicit required |197|-------------|-------------------|198| Django, Flask, FastAPI, Starlette, AIOHTTP, Tornado, Quart, Falcon, Sanic, Bottle | `DramatiqIntegration` |199| Celery, RQ, Huey, ARQ | `GRPCIntegration` |200| SQLAlchemy, Redis, asyncpg, pymongo | `StrawberryIntegration` |201| Requests, HTTPX, aiohttp-client | `AsyncioIntegration` |202| OpenAI, Anthropic, LangChain, Pydantic AI, MCP | `OpenTelemetryIntegration` |203| Python `logging`, Loguru | `WSGIIntegration` / `ASGIIntegration` |204205### For Each Agreed Feature206207Walk through features one at a time. Load the reference, follow its steps, verify before moving on:208209| Feature | Reference file | Load when... |210|---------|---------------|-------------|211| Error Monitoring | `${SKILL_ROOT}/references/error-monitoring.md` | Always (baseline) |212| Tracing | `${SKILL_ROOT}/references/tracing.md` | HTTP handlers / distributed tracing |213| Profiling | `${SKILL_ROOT}/references/profiling.md` | Performance-sensitive production |214| Logging | `${SKILL_ROOT}/references/logging.md` | Always; enhanced for Loguru |215| Metrics | `${SKILL_ROOT}/references/metrics.md` | Business KPIs / SLO tracking |216| Crons | `${SKILL_ROOT}/references/crons.md` | Scheduler / cron patterns detected |217| AI Monitoring | `${SKILL_ROOT}/references/ai-monitoring.md` | AI library detected |218219For each feature: `Read ${SKILL_ROOT}/references/<feature>.md`, follow steps exactly, verify it works.220221---222223## Configuration Reference224225### Key `sentry_sdk.init()` Options226227| Option | Type | Default | Purpose |228|--------|------|---------|---------|229| `dsn` | `str` | `None` | SDK disabled if empty; env: `SENTRY_DSN` |230| `environment` | `str` | `"production"` | e.g., `"staging"`; env: `SENTRY_ENVIRONMENT` |231| `release` | `str` | `None` | e.g., `"myapp@1.0.0"`; env: `SENTRY_RELEASE` |232| `send_default_pii` | `bool` | `False` | Include IP, headers, cookies, auth user |233| `traces_sample_rate` | `float` | `None` | Transaction sample rate; `None` disables tracing |234| `traces_sampler` | `Callable` | `None` | Custom per-transaction sampling (overrides rate) |235| `profile_session_sample_rate` | `float` | `None` | Continuous profiling session rate |236| `profile_lifecycle` | `str` | `"manual"` | `"trace"` = auto-start profiler with spans |237| `profiles_sample_rate` | `float` | `None` | Transaction-based profiling rate |238| `enable_logs` | `bool` | `False` | Send logs to Sentry (SDK ≥ 2.35.0) |239| `sample_rate` | `float` | `1.0` | Error event sample rate |240| `attach_stacktrace` | `bool` | `False` | Stack traces on `capture_message()` |241| `max_breadcrumbs` | `int` | `100` | Max breadcrumbs per event |242| `debug` | `bool` | `False` | Verbose SDK debug output |243| `before_send` | `Callable` | `None` | Hook to mutate/drop error events |244| `before_send_transaction` | `Callable` | `None` | Hook to mutate/drop transaction events |245| `ignore_errors` | `list` | `[]` | Exception types or regex patterns to suppress |246| `auto_enabling_integrations` | `bool` | `True` | Set `False` to disable all auto-detection |247248### Environment Variables249250| Variable | Maps to | Notes |251|----------|---------|-------|252| `SENTRY_DSN` | `dsn` | |253| `SENTRY_RELEASE` | `release` | Also auto-detected from git SHA, Heroku, CircleCI, CodeBuild, GAE |254| `SENTRY_ENVIRONMENT` | `environment` | |255| `SENTRY_DEBUG` | `debug` | |256257---258259## Verification260261Test that Sentry is receiving events:262263```python264# Trigger a real error event — check dashboard within seconds265division_by_zero = 1 / 0266```267268Or for a non-crashing check:269```python270sentry_sdk.capture_message("Sentry Python SDK test")271```272273If nothing appears:2741. Set `debug=True` in `sentry_sdk.init()` — prints SDK internals to stdout2752. Verify the DSN is correct2763. Check `SENTRY_DSN` env var is set in the running process2774. For Celery/RQ: ensure init runs in the **worker** process, not just the calling process278279---280281## Phase 4: Cross-Link282283After completing Python setup, check for a companion frontend missing Sentry:284285```bash286ls frontend/ web/ client/ ui/ 2>/dev/null287cat frontend/package.json web/package.json client/package.json 2>/dev/null \288 | grep -E '"react"|"svelte"|"vue"|"next"|"nuxt"'289```290291If a frontend exists without Sentry, suggest the matching skill:292293| Frontend detected | Suggest skill |294|-------------------|--------------|295| React / Next.js | `sentry-react-sdk` |296| Svelte / SvelteKit | `sentry-svelte-sdk` |297| Vue / Nuxt | Use `@sentry/vue` — see [docs.sentry.io/platforms/javascript/guides/vue/](https://docs.sentry.io/platforms/javascript/guides/vue/) |298| Other JS/TS | `sentry-react-sdk` (covers generic browser JS patterns) |299300---301302## Troubleshooting303304| Issue | Solution |305|-------|----------|306| Events not appearing | Set `debug=True`, verify DSN, check env vars in the running process |307| Malformed DSN error | Format: `https://<key>@o<org>.ingest.sentry.io/<project>` |308| Django exceptions not captured | Ensure `sentry_sdk.init()` is at the **top** of `settings.py` before other imports |309| Flask exceptions not captured | Init must happen **before** `app = Flask(__name__)` |310| FastAPI exceptions not captured | Init before `app = FastAPI()`; both `StarletteIntegration` and `FastApiIntegration` auto-enabled |311| Celery task errors not captured | Must call `sentry_sdk.init()` in the **worker process** via `celeryd_init` signal |312| Sanic init not working | Init must be inside `@app.listener("before_server_start")`, not module level |313| uWSGI not capturing | Add `--enable-threads --py-call-uwsgi-fork-hooks` to uWSGI command |314| No traces appearing | Verify `traces_sample_rate` is set (not `None`); check that the integration is auto-enabled |315| Profiling not starting | Requires `traces_sample_rate > 0` + either `profile_session_sample_rate` or `profiles_sample_rate` |316| `enable_logs` not working | Requires SDK ≥ 2.35.0; for direct structured logs use `sentry_sdk.logger`; for stdlib bridging use `LoggingIntegration(sentry_logs_level=...)` |317| Too many transactions | Lower `traces_sample_rate` or use `traces_sampler` to drop health checks |318| Cross-request data leaking | Don't use `get_global_scope()` for per-request data — use `get_isolation_scope()` |319| RQ worker not reporting | Pass `--sentry-dsn=""` to disable RQ's own Sentry shortcut; init via settings file instead |