ref: remove old sentry logs to error handler documentation

Author: Litarnus

docs/platforms/php/common/integrations/monolog.mdx

@@ -1,27 +1,24 @@
 ---
 title: Monolog
-description: "Learn how to enable Sentry's PHP SDK to capture Monolog events and logs."
+description: "Learn how to use Monolog with Sentry's PHP SDK."
 ---
 
 <Alert level="info" title="Sentry Logs">
 
-  Enable the Sentry Logs feature with `\Sentry\init(['enable_logs' => true])` to unlock Sentry's full logging power. With Sentry Logs, you can search, filter, and analyze logs from across your entire application in one place.
+Enable the Sentry Logs feature with `\Sentry\init(['enable_logs' => true])` to unlock Sentry's full logging power. With Sentry Logs, you can search, filter, and analyze logs from across your entire application in one place.
 
 </Alert>
 
-When using [Monolog](https://github.com/Seldaek/monolog) you can configure handlers to capture Monolog messages in several ways:
+When using [Monolog](https://github.com/Seldaek/monolog), you can configure handlers to capture Monolog messages in Sentry. The examples below show common patterns for sending structured logs and recording breadcrumbs:
 
 - **Logs Handler** - Send structured logs to Sentry
-- **Event Handler** - Capture messages as error events in Sentry
 - **Breadcrumb Handler** - Record messages as breadcrumbs attached to future events
 
-The breadcrumb handler will not send anything to Sentry directly, it only records breadcrumbs that will be attached to any event or exception sent to Sentry.
+The breadcrumb handler does not send anything to Sentry directly. It records breadcrumbs that are attached to a later event or exception.
 
 ## Logs
 
-<Alert level="info">
-Available in SDK version 4.12.0 and above.
-</Alert>
+<Alert level="info">Available in SDK version 4.12.0 and above.</Alert>
 
 To send structured logs to Sentry, use the `\Sentry\Monolog\LogsHandler`.
 
@@ -58,55 +55,30 @@ $logger->warning('API rate limit approaching', [
 
 The context array passed to Monolog methods becomes searchable attributes in the Sentry logs interface.
 
-## Events & Breadcrumbs
+## Breadcrumbs
+
+Use the breadcrumb handler when you want Monolog messages attached to future Sentry events for extra context.
 
 ```php
 <?php
 
 use Monolog\Level;
 use Monolog\Logger;
-use Monolog\Handler\StreamHandler;
 
-// Setup the Sentry SDK, this can also be done elsewhere in your application
+// Set up the Sentry SDK, this can also be done elsewhere in your application
 \Sentry\init([
-    'dsn' => '___PUBLIC_DSN___'
+    'dsn' => '___PUBLIC_DSN___',
 ]);
 
-// Create a Monolog channel with a breadcrumb handler and a Sentry handler
+// Create a Monolog channel with a breadcrumb handler
 $log = new Logger('sentry');
 $log->pushHandler(new \Sentry\Monolog\BreadcrumbHandler(
     hub: \Sentry\SentrySdk::getCurrentHub(),
-    level: Level::Info, // Take note of the level here, messages with that level or higher will be attached to future Sentry events as breadcrumbs
-));
-$log->pushHandler(new \Sentry\Monolog\Handler(
-    hub: \Sentry\SentrySdk::getCurrentHub(),
-    level: Level::Error, // Take note of the level here, messages with that level or higher will be sent to Sentry
-    bubble: true,
-    fillExtraContext: false, // Will add a `monolog.context` & `monolog.extra`, key to the event with the Monolog `context` & `extra` values
+    level: Level::Info, // Messages with this level or higher will be attached to future Sentry events as breadcrumbs
 ));
 
-// Log an error:
-$log->error('Something bad happened');
-
-// To log an exception you can use the following code:
-try {
-    throw new RuntimeException('Some exception');
-} catch (RuntimeException $exception) {
-    $log->error('Some exception happened', ['exception' => $exception]);
-}
-```
-
-## Support With Sentry Logs
-
-Monolog logs can also be captured as <PlatformLink to="/logs/">Sentry Logs</PlatformLink> for better searchability and querying.
-
-To enable this, set `enable_logs` to `true` when initializing the SDK:
-
-```php
-\Sentry\init([
-    'dsn' => '___PUBLIC_DSN___',
-    'enable_logs' => true,
+$log->info('Starting checkout flow');
+$log->warning('API rate limit approaching', [
+    'endpoint' => '/api/users',
 ]);
 ```
-
-You can control which log levels are sent to Sentry Logs by configuring the Monolog handler's minimum level.

docs/platforms/php/guides/laravel/index.mdx

@@ -10,10 +10,10 @@ og_image: /og-images/platforms-php-guides-laravel.png
 
 ## Prerequisites
 
-* You need a [Sentry account](https://sentry.io/signup/) and project
-* Your Laravel application needs to run on PHP 7.2 or later
-* Your Laravel version needs to be 11.x or higher
-* Read one of these guides if you use an [older version](/platforms/php/guides/laravel/other-versions/) or need [Lumen-specific instructions](/platforms/php/guides/laravel/other-versions/lumen/)
+- You need a [Sentry account](https://sentry.io/signup/) and project
+- Your Laravel application needs to run on PHP 7.2 or later
+- Your Laravel version needs to be 11.x or higher
+- Read one of these guides if you use an [older version](/platforms/php/guides/laravel/other-versions/) or need [Lumen-specific instructions](/platforms/php/guides/laravel/other-versions/lumen/)
 
 ## Install
 
@@ -48,7 +48,7 @@ return Application::configure(basePath: dirname(__DIR__))
     ->create();
 ```
 
-Alternatively, you can configure Sentry as a [Laravel Log Channel](usage/#log-channels).
+If you also want to send structured logs to Sentry, see the [Logs guide](logs/).
 
 ## Configure
 
@@ -65,7 +65,8 @@ SENTRY_LARAVEL_DSN=___PUBLIC_DSN___
 ```
 
 <Alert level="warning">
-  In order to receive stack trace arguments in your errors, make sure to set `zend.exception_ignore_args: Off` in your php.ini
+  In order to receive stack trace arguments in your errors, make sure to set
+  `zend.exception_ignore_args: Off` in your php.ini
 </Alert>
 
 ## Verify

docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx

@@ -30,30 +30,25 @@ public function register(): void
 }
 ```
 
-<Alert>
-
-Alternatively, you can configure Sentry in your [Laravel Log Channel](/platforms/php/guides/laravel/usage/#log-channels), allowing you to log `info` and `debug` as well.
-
-</Alert>
+If you also want to send structured logs to Sentry, see the [Logs guide](/platforms/php/guides/laravel/logs/).
 
 ## Configure
 
 Configure the Sentry DSN with this command:
 
-
 ```shell
 php artisan sentry:publish --dsn=___PUBLIC_DSN___
 ```
 
 It creates the config file (`config/sentry.php`) and adds the `DSN` to your `.env` file.
 
-
 ```shell {filename:.env}
 SENTRY_LARAVEL_DSN=___PUBLIC_DSN___
 ```
 
 <Alert level="warning">
-  In order to receive stack trace arguments in your errors, make sure to set `zend.exception_ignore_args: Off` in your php.ini
+  In order to receive stack trace arguments in your errors, make sure to set
+  `zend.exception_ignore_args: Off` in your php.ini
 </Alert>
 
 ## Verify

docs/platforms/php/guides/laravel/usage/index.mdx

@@ -89,50 +89,6 @@ class SentryContext
 }
 ```
 
-### Log Channels
-
-<Alert title="Note">
-
-If you're using log channels to log your exceptions and are also logging exceptions to Sentry in your exception handler, exceptions might show up in Sentry twice.
-
-</Alert>
-
-To configure Sentry as a log channel, add the following config to the `channels` section in `config/logging.php`.
-If this file does not exist, run `php artisan config:publish logging` to publish it.
-
-```php {filename:config/logging.php}
-'channels' => [
-    // ...
-    'sentry' => [
-        'driver' => 'sentry',
-    ],
-],
-```
-
-After you configured the Sentry log channel, you can configure your app to both log to a log file and to Sentry by modifying the log stack:
-
-```bash {filename:.env}
-# ...
-LOG_CHANNEL=stack
-LOG_STACK=single,sentry
-# ...
-```
-
-Optionally, you can set the [logging level](https://laravel.com/docs/8.x/logging#log-levels) and if events should bubble on the driver:
-
-```php {filename:config/logging.php}
-'channels' => [
-    // ...
-    'sentry' => [
-        'driver' => 'sentry',
-        // The minimum logging level at which this handler will be triggered
-        // Available levels: debug, info, notice, warning, error, critical, alert, emergency
-        'level' => env('LOG_LEVEL', 'error'),
-        'bubble' => true, // Whether the messages that are handled can bubble up the stack or not
-    ],
-],
-```
-
 ### Queue Jobs
 
 When you have defined a `failed` method on your job class ([documentation](https://laravel.com/docs/8.x/queues#cleaning-up-after-failed-jobs)), that failed method acts as if your job runs inside a `try {} catch (\Exception $e) {}`. This will prevent reporting exception, causing the job to have failed to be reported to Sentry.
@@ -157,32 +113,6 @@ public function failed(\Exception $exception)
 }
 ```
 
-#### Naming Your Log Channels
-
-To filter on multiple log channels inside Sentry, you can add the `name` attribute to the log channel.
-It will show up in Sentry as the `logger` tag, which is filterable.
-
-For example:
-
-```php {filename:config/logging.php}
-'channels' => [
-    'my_stacked_channel' => [
-        'driver' => 'stack',
-        'channels' => ['single', 'sentry'],
-        'name' => 'my-channel'
-    ],
-    //...
-],
-```
-
-As a result, you can log errors to your channel:
-
-```php
-\Log::channel('my_stacked_channel')->error('My error');
-```
-
-And Sentry's `logger` tag now has the channel's `name`. You can filter on the "my-channel" value.
-
 ### Resolve Name Conflicts
 
 If you have other packages also named Sentry, you'll need to create your own service provider extending ours so we can prevent naming conflicts.

docs/platforms/php/guides/symfony/index.mdx

@@ -6,8 +6,8 @@ description: "Symfony is a set of reusable PHP components and a PHP framework to
 
 ## Prerequisites
 
-* You need a [Sentry account](https://sentry.io/signup/) and project
-* Your Symfony application needs to run on PHP 7.2 or later
+- You need a [Sentry account](https://sentry.io/signup/) and project
+- Your Symfony application needs to run on PHP 7.2 or later
 
 ## Install
 
@@ -17,7 +17,7 @@ Install the `sentry/sentry-symfony` bundle:
 composer require sentry/sentry-symfony
 ```
 
-If you are using [Monolog](https://github.com/Seldaek/monolog) to report events instead of the typical error listener approach, you need this [additional configuration](integrations/monolog/) to log the errors correctly.
+If you're already using [Monolog](https://github.com/Seldaek/monolog), see the [Monolog integration docs](integrations/monolog/) for Monolog-related configuration.
 
 ## Configure
 
@@ -32,41 +32,33 @@ SENTRY_DSN="___PUBLIC_DSN___"
 When using Symfony Flex, the Sentry bundle is configured to be enabled in the `prod` environment only by default. You can change this behaviour in your `config/packages/sentry.yaml` and `config/bundles.php` files.
 
 <Alert level="warning">
-  In order to receive stack trace arguments in your errors, make sure to set `zend.exception_ignore_args: Off` in your php.ini
+  In order to receive stack trace arguments in your errors, make sure to set
+  `zend.exception_ignore_args: Off` in your php.ini
 </Alert>
 
 ## Verify
 
-To test that both logger error and exception are correctly sent to sentry.io, you can create the following controller:
+To test that Sentry is capturing unhandled exceptions, you can create the following controller:
 
 ```php
 <?php
 
 namespace App\Controller;
 
-use Psr\Log\LoggerInterface;
 use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
 use Symfony\Component\Routing\Attribute\Route;
 
 class SentryTestController extends AbstractController
 {
-    public function __construct(private LoggerInterface $logger)
-    {
-    }
-
     #[Route('/_sentry-test', name: 'sentry_test')]
-    public function testLog()
+    public function testException()
     {
-        // the following code will test if monolog integration logs to sentry
-        $this->logger->error('My custom logged error.', ['some' => 'Context Data']);
-
-        // the following code will test if an uncaught exception logs to sentry
         throw new \RuntimeException('Example exception.');
     }
 }
 ```
 
-After you visit the `/_sentry-test` page, you can view and resolve the recorded error by logging into [sentry.io](https://sentry.io) and opening your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
+After you visit the `/_sentry-test` page, you can view and resolve the recorded error by logging into [sentry.io](https://sentry.io) and opening your project.
 
 ## Next Steps