[skill-drift] sentry-php-sdk may need updates

[github-actions]

cc @getsentry/team-web-sdk-backend

SDK Changes Detected

The following PRs were merged to getsentry/sentry-php in the last 7 days that may affect the sentry-php-sdk skill:

• feat(otel): add OTLP integration sentry-php#2030 — feat(otel): add OTLP integration (feat(otel): add OTLP integration sentry-php#2030)
• feat(logs): add log_flush_threshold flag to trigger auto flush sentry-php#2032 — feat(logs): add log_flush_threshold flag to trigger auto flush (feat(logs): add log_flush_threshold flag to trigger auto flush sentry-php#2032)

Potential Skill Gaps

1. New Integration: PR #2030 adds OTLPIntegration — a new integration class that enables OTLP trace support. Usage requires adding it to the integrations array in Sentry\init(). This is not mentioned anywhere in the skill or its reference files.

   \Sentry\init([
       'dsn' => '___PUBLIC_DSN___',
       'integrations' => [
           new \Sentry\Integration\OTLPIntegration(),
       ],
   ]);

   Note: OTLP tracing and Sentry tracing cannot be used simultaneously.

2. New Config Option: PR #2032 adds a log_flush_threshold init option (default: null) that triggers auto-flush of buffered Sentry Logs when the buffer reaches the threshold count. Not present in references/logging.md config options.

   \Sentry\init([
       'dsn' => '__YOUR_DSN__',
       'log_flush_threshold' => 50,  // flush after 50 buffered log records
   ]);

Skill Files to Review

• skills/sentry-php-sdk/SKILL.md
• skills/sentry-php-sdk/references/logging.md

Priority

HIGH — New integration with significant behavioral implications (OTLP vs Sentry tracing mutual exclusivity) and new config option affecting log delivery reliability.

Generated by SDK Skill Drift Detector · ◷

• expires on Apr 6, 2026, 11:02 PM UTC

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #75

View newer issue

---

This action was performed automatically by the SDK Skill Drift Detector workflow.