Skip to content

[skill-drift] sentry-php-sdk: LogToSentryIssueHandler (Monolog → Sentry issues) missing from logging reference #121

@github-actions

Description

@github-actions

Skill Drift Report

Skill file: skills/sentry-php-sdk/references/logging.md
SDK repo PR: getsentry/sentry-php#2075
Merged: 2026-04-29

What Changed in the SDK

PR #2075 added LogToSentryIssueHandler — a new Monolog handler that captures log messages as Sentry error issues (not structured logs). This is distinct from the existing LogsHandler which routes to the Sentry Logs product.

The current skills/sentry-php-sdk/references/logging.md already documents LogsHandler and ExceptionToSentryIssueHandler but does not mention LogToSentryIssueHandler.

Required Skill Update

Add a section to skills/sentry-php-sdk/references/logging.md covering LogToSentryIssueHandler:

Handler comparison table (update or add)

Handler Routes to Use case
LogsHandler Sentry Logs product Structured log search/exploration
ExceptionToSentryIssueHandler Sentry Issues Capture exceptions thrown during logging
LogToSentryIssueHandler Sentry Issues Capture log messages (non-exception) as issues

Usage example

use Monolog\Level;
use Monolog\Logger;
use Sentry\Monolog\LogToSentryIssueHandler;

\Sentry\init(['dsn' => '...']);

$log = new Logger('app');
$log->pushHandler(new LogToSentryIssueHandler(
    hub: \Sentry\SentrySdk::getCurrentHub(),
    level: Level::Error,
));

$log->error('Critical background job failed', ['job_id' => $jobId]);
// → creates a Sentry Issue (not a structured log)

Note: LogToSentryIssueHandler vs LogsHandler — clarify which to use when the goal is alertable issues vs. searchable logs.

Note

🔒 Integrity filter blocked 16 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #282 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #499 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #500 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #7868 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #7847 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #4224 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #1168 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #893 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #6184 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #4793 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #6140 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #6139 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #6138 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #2411 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #2938 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #2182 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by SDK Skill Drift Detector · ● 442K ·

  • expires on May 18, 2026, 7:53 PM UTC

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions