sentry-php-sdk
Skill19 starsChanged 57 days agoMITView on GitHub
Full Sentry SDK setup for PHP. Use when asked to "add Sentry to PHP", "install sentry/sentry", "setup Sentry in PHP", or configure error monitoring, tracing, profiling, logging, metrics, crons, or AI monitoring for PHP applications. Supports plain PHP, Laravel, and Symfony.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- getsentry/sentry-for-aiword for word, first seen Oct 13, 2026
- gerald-donkor/poli-intelword for word, first seen Oct 11, 2026
Other versions2 projects use a version of this.
Word for word · 2
- getsentry/sentry-for-ai★ 276100% same
- gerald-donkor/poli-intel★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository87 other files it gives its agents.
- .agents/skills/vercel-optimize/AGENTS.mdAGENTS.md
- block-kitSkill
- cloudflare-deploySkill
- connect-recommendSkill
- connect-required-verification-informationSkill
- create-slack-appSkill
- deploy-to-vercelSkill
- gws-calendar-agendaSkill
- gws-calendar-insertSkill
- gws-calendarSkill
- gws-chat-sendSkill
- gws-chatSkill
- gws-docsSkill
- gws-docs-writeSkill
- gws-driveSkill
- gws-drive-uploadSkill
- gws-gmail-forwardSkill
- gws-gmail-readSkill
- gws-gmail-reply-allSkill
- gws-gmail-replySkill
- gws-gmail-sendSkill
- gws-gmailSkill
- gws-gmail-triageSkill
- gws-gmail-watchSkill
- gws-peopleSkill
- gws-sharedSkill
- gws-sheets-appendSkill
- gws-sheets-readSkill
- gws-sheetsSkill
- gws-tasksSkill
- gws-workflow-email-to-taskSkill
- gws-workflow-file-announceSkill
- gws-workflow-meeting-prepSkill
- gws-workflowSkill
- gws-workflow-standup-reportSkill
- gws-workflow-weekly-digestSkill
- linearSkill
- netlify-deploySkill
- notion-knowledge-captureSkill
- notion-meeting-intelligenceSkill
- notion-research-documentationSkill
- notion-spec-to-implementationSkill
- rampSkill
- render-deploySkill
- sentry-android-sdkSkill
- sentry-browser-sdkSkill
- sentry-cloudflare-sdkSkill
- sentry-cocoa-sdkSkill
- sentry-create-alertSkill
- sentry-debug-issueSkill
- sentry-dotnet-sdkSkill
- sentry-elixir-sdkSkill
- sentry-fix-issuesSkill
- sentry-flutter-sdkSkill
- sentry-get-startedSkill
- sentry-go-sdkSkill
- sentry-nestjs-sdkSkill
- sentry-nextjs-sdkSkill
- sentry-node-sdkSkill
- sentry-python-sdkSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Run these commands to understand the project before making recommendations:
- Very specific: line 121
Place \Sentry\init() at the top of your entry point (index.php, bootstrap.php, or equivalent), before any application code:
- Distinctive: line 287
Test that Sentry is receiving events:
- Very specific: line 313
Verify the DSN is correct (format: https://<key>@o<org>.ingest.sentry.io/<project>)
- Very specific: line 314
Check SENTRY_DSN (or SENTRY_LARAVEL_DSN) env var is set in the running process
- Distinctive: line 321
After completing PHP setup, check for a companion frontend missing Sentry:
- Distinctive: line 329
If a frontend exists without Sentry, suggest the matching skill:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
All Skills > SDK Setup > PHP SDK
Sentry PHP SDK
Opinionated wizard that scans your PHP project and guides you through complete Sentry setup.
Invoke This Skill When
- User asks to "add Sentry to PHP" or "setup Sentry" in a PHP app
- User wants error monitoring, tracing, profiling, logging, metrics, or crons in PHP
- User mentions
sentry/sentry,sentry/sentry-laravel,sentry/sentry-symfony, or Sentry + any PHP framework - User wants to monitor Laravel routes, Symfony controllers, queues, scheduled tasks, or plain PHP scripts
Note: SDK versions and APIs below reflect Sentry docs at time of writing (sentry/sentry 4.x, sentry/sentry-laravel 4.x, sentry/sentry-symfony 5.x). Always verify against docs.sentry.io/platforms/php/ before implementing.
Phase 1: Detect
Run these commands to understand the project before making recommendations:
# Check existing Sentry
grep -i sentry composer.json composer.lock 2>/dev/null
# Detect framework
cat composer.json | grep -E '"laravel/framework"|"symfony/framework-bundle"|"illuminate/'
# Confirm framework via filesystem markers
ls artisan 2>/dev/null && echo "Laravel detected"
ls bin/console 2>/dev/null && echo "Symfony detected"
# Detect queue systems
grep -E '"laravel/horizon"|"symfony/messenger"' composer.json 2>/dev/null
# Detect AI libraries
grep -E '"(laravel/ai|openai-php|openai/|anthropic|llm)' composer.json 2>/dev/null
# Check for companion frontend
ls frontend/ resources/js/ assets/ 2>/dev/null
cat package.json 2>/dev/null | grep -E '"react"|"svelte"|"vue"|"next"'What to note:
- Is
sentry/sentry(or-laravel/-symfony) already incomposer.json? If yes, check if the init call exists — may just need feature config. - Framework detected? Laravel (has
artisan+laravel/frameworkin composer.json), Symfony (hasbin/console+symfony/framework-bundle), or plain PHP. - Queue system? (Laravel Queue / Horizon, Symfony Messenger need queue worker configuration.)
- AI libraries? (
laravel/aiis auto-instrumented bysentry/sentry-laravel >= 4.27.0when tracing is enabled; other PHP AI libraries need manual spans.) - 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 and PHP errors
- ✅ Logging — Monolog integration (Laravel/Symfony auto-configure; plain PHP uses
MonologHandler)
Recommend when detected:
- ✅ Tracing — web framework detected (Laravel/Symfony auto-instrument HTTP, DB, Twig/Blade, cache)
- ⚡ Profiling — production apps where performance matters (requires
excimerPHP extension, Linux/macOS only) - ⚡ Crons — scheduler patterns detected (Laravel Scheduler, Symfony Scheduler, custom cron jobs)
- ⚡ Metrics — business KPIs or SLO tracking (uses
TraceMetricsAPI) - ✅ AI Monitoring —
laravel/aidetected in a Laravel app (auto-instrumented insentry/sentry-laravel >= 4.27.0)
Recommendation matrix:
| Feature | Recommend when... | Reference |
| Error Monitoring | Always — non-negotiable baseline | ${SKILL_ROOT}/references/error-monitoring.md |
| Tracing | Laravel/Symfony detected, or manual spans needed | ${SKILL_ROOT}/references/tracing.md |
| Profiling | Production + excimer extension available | ${SKILL_ROOT}/references/profiling.md |
| Logging | Always; Monolog for Laravel/Symfony | ${SKILL_ROOT}/references/logging.md |
| Metrics | Business events or SLO tracking needed | ${SKILL_ROOT}/references/metrics.md |
| Crons | Scheduler or cron patterns detected | ${SKILL_ROOT}/references/crons.md |
| AI Monitoring | laravel/ai detected in a Laravel app, or manual PHP AI spans needed | ${SKILL_ROOT}/references/ai-monitoring.md |
Propose: "I recommend Error Monitoring + Tracing [+ Logging]. Want Profiling, Crons, Metrics, or AI Monitoring too?"
Phase 3: Guide
Install
# Plain PHP
composer require sentry/sentry "^4.0"
# Laravel
composer require sentry/sentry-laravel "^4.0"
# Laravel with Laravel AI monitoring
composer require sentry/sentry-laravel "^4.27.0"
# Symfony
composer require sentry/sentry-symfony "^5.0"System requirements:
- PHP 7.2 or later
- Extensions:
ext-json,ext-mbstring,ext-curl(all required) excimerPECL extension (Linux/macOS only — required for profiling)
Framework-Specific Initialization
Plain PHP
Place \Sentry\init() at the top of your entry point (index.php, bootstrap.php, or equivalent), before any application code:
<?php
require_once 'vendor/autoload.php';
\Sentry\init([
'dsn' => $_SERVER['SENTRY_DSN'] ?? '',
'environment' => $_SERVER['SENTRY_ENVIRONMENT'] ?? 'production',
'release' => $_SERVER['SENTRY_RELEASE'] ?? null,
'send_default_pii' => true,
'traces_sample_rate' => 1.0,
'profiles_sample_rate' => 1.0,
'enable_logs' => true,
]);
// rest of application...Laravel
Step 1 — Register exception handler in bootstrap/app.php:
use Sentry\Laravel\Integration;
return Application::configure(basePath: dirname(__DIR__))
->withExceptions(function (Exceptions $exceptions) {
Integration::handles($exceptions);
})->create();Step 2 — Publish config and set DSN:
php artisan sentry:publish --dsn=YOUR_DSNThis creates config/sentry.php and adds SENTRY_LARAVEL_DSN to .env.
Step 3 — Configure .env:
SENTRY_LARAVEL_DSN=https://examplePublicKey@o0.ingest.sentry.io/0
SENTRY_TRACES_SAMPLE_RATE=1.0
SENTRY_PROFILES_SAMPLE_RATE=1.0For full Laravel configuration options, read
${SKILL_ROOT}/references/laravel.md.
Symfony
Step 1 — Register the bundle in config/bundles.php (auto-done by Symfony Flex):
Sentry\SentryBundle\SentryBundle::class => ['all' => true],Step 2 — Create config/packages/sentry.yaml:
sentry:
dsn: '%env(SENTRY_DSN)%'
options:
environment: '%env(APP_ENV)%'
release: '%env(SENTRY_RELEASE)%'
send_default_pii: true
traces_sample_rate: 1.0
profiles_sample_rate: 1.0
enable_logs: trueStep 3 — Set the DSN in .env:
SENTRY_DSN=https://examplePublicKey@o0.ingest.sentry.io/0For full Symfony configuration options, read
${SKILL_ROOT}/references/symfony.md.
Quick Start — Recommended Init (Plain PHP)
Full init enabling the most features with sensible defaults:
\Sentry\init([
'dsn' => $_SERVER['SENTRY_DSN'] ?? '',
'environment' => $_SERVER['SENTRY_ENVIRONMENT'] ?? 'production',
'release' => $_SERVER['SENTRY_RELEASE'] ?? null,
'send_default_pii' => true,
// Tracing (lower to 0.1–0.2 in high-traffic production)
'traces_sample_rate' => 1.0,
// Profiling — requires excimer extension (Linux/macOS only)
'profiles_sample_rate' => 1.0,
// Structured logs (sentry/sentry >=4.12.0)
'enable_logs' => true,
]);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; Monolog for Laravel/Symfony |
| 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 | laravel/ai detected in Laravel, or manual PHP AI spans needed |
For each feature: Read ${SKILL_ROOT}/references/<feature>.md, follow steps exactly, verify it works.
Configuration Reference
Key \Sentry\init() Options (Plain PHP)
| Option | Type | Default | Purpose |
dsn | string|bool|null | $_SERVER['SENTRY_DSN'] | SDK disabled if empty or false |
environment | string|null | $_SERVER['SENTRY_ENVIRONMENT'] | e.g., "staging" |
release | string|null | $_SERVER['SENTRY_RELEASE'] | e.g., "myapp@1.0.0" |
send_default_pii | bool | false | Include request headers, cookies, IP |
sample_rate | float | 1.0 | Error event sample rate (0.0–1.0) |
traces_sample_rate | float|null | null | Transaction sample rate; null disables tracing |
traces_sampler | callable|null | null | Custom per-transaction sampling (overrides rate) |
profiles_sample_rate | float|null | null | Profiling rate relative to traces; requires excimer |
enable_logs | bool | false | Send structured logs to Sentry (>=4.12.0) |
max_breadcrumbs | int | 100 | Max breadcrumbs per event |
attach_stacktrace | bool | false | Stack traces on captureMessage() |
in_app_include | string[] | [] | Path prefixes belonging to your app |
in_app_exclude | string[] | [] | Path prefixes for third-party code (hidden in traces) |
ignore_exceptions | string[] | [] | Exception FQCNs to never report |
ignore_transactions | string[] | [] | Transaction names to never report |
error_types | int|null | error_reporting() | PHP error bitmask (e.g., E_ALL & ~E_NOTICE) |
capture_silenced_errors | bool | false | Capture errors suppressed by @ operator |
max_request_body_size | string | "medium" | "none" / "small" / "medium" / "always" |
before_send | callable | identity | fn(Event $event, ?EventHint $hint): ?Event — return null to drop |
before_breadcrumb | callable | identity | fn(Breadcrumb $b): ?Breadcrumb — return null to discard |
trace_propagation_targets | string[]|null | null | Downstream hosts to inject sentry-trace headers into; null = all, [] = none |
strict_trace_continuation | bool | false | Only continue an incoming distributed trace if the sentry-org_id baggage matches the SDK's org ID; prevents trace contamination from third-party Sentry-instrumented services (>=4.21.0) |
debug | bool | false | Verbose SDK output (use a PSR-3 logger option instead for structured output) |
Environment Variables
| Variable | Maps to | Notes |
SENTRY_DSN | dsn | Also $_SERVER['SENTRY_DSN'] |
SENTRY_ENVIRONMENT | environment | |
SENTRY_RELEASE | release | Also reads $_SERVER['AWS_LAMBDA_FUNCTION_VERSION'] |
SENTRY_SPOTLIGHT | spotlight |
Laravel note: Uses
SENTRY_LARAVEL_DSN(falls back toSENTRY_DSN). Other options followSENTRY_TRACES_SAMPLE_RATE,SENTRY_PROFILES_SAMPLE_RATE, etc.
Verification
Test that Sentry is receiving events:
// Trigger a real error event — check the Sentry dashboard within seconds
throw new \Exception('Sentry PHP SDK test');Or for a non-crashing check:
\Sentry\captureMessage('Sentry PHP SDK test');Laravel:
php artisan sentry:testIf nothing appears:
- Enable debug output:
\Sentry\init([ 'dsn' => '...', 'logger' => new \Sentry\Logger\DebugStdOutLogger(), ]); - Verify the DSN is correct (format:
https://<key>@o<org>.ingest.sentry.io/<project>) - Check
SENTRY_DSN(orSENTRY_LARAVEL_DSN) env var is set in the running process - For queue workers: ensure Sentry is initialized inside the worker process, not just the web process
Phase 4: Cross-Link
After completing PHP setup, check for a companion frontend missing Sentry:
ls frontend/ resources/js/ assets/ public/ 2>/dev/null
cat package.json frontend/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 | Enable logger option (DebugStdOutLogger), verify DSN, check env vars in the running process |
| Malformed DSN error | Format: https://<key>@o<org>.ingest.sentry.io/<project> |
| Laravel exceptions not captured | Ensure Integration::handles($exceptions) is in bootstrap/app.php |
| Symfony exceptions not captured | Verify SentryBundle is registered in config/bundles.php |
| No traces appearing | Set traces_sample_rate (not null); confirm auto-instrumentation is enabled |
| Profiling not working | excimer extension required (Linux/macOS only; not available on Windows); requires traces_sample_rate > 0 |
enable_logs not working | Requires sentry/sentry >= 4.12.0, sentry/sentry-laravel >= 4.15.0, or sentry/sentry-symfony >= 5.4.0 |
| Queue worker errors missing | Init Sentry in the worker process itself, not just the web process; for Laravel use SENTRY_LARAVEL_DSN in worker .env |
| Too many transactions | Lower traces_sample_rate or use traces_sampler to drop health check routes |
| PII not captured | Set send_default_pii: true; for Laravel set send_default_pii: true in config/sentry.php |
@-suppressed errors missing | Set capture_silenced_errors: true |
| Cross-service traces broken | Check trace_propagation_targets; ensure downstream services have Sentry installed |
| Trace contamination from third-party services | Set strict_trace_continuation: true to only continue traces where the incoming sentry-org_id baggage matches your SDK's org ID (>=4.21.0) |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

