From 4fa3b09ecbcf42f35b688d2cba73c8f20a04bc8e Mon Sep 17 00:00:00 2001 From: Abhijeet Prasad Date: Tue, 5 Aug 2025 16:33:51 -0400 Subject: [PATCH] Switch from `sentry` -> `sentry_logs` for laravel logs channel --- platform-includes/logs/usage/php.laravel.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/platform-includes/logs/usage/php.laravel.mdx b/platform-includes/logs/usage/php.laravel.mdx index 13e39224b1ab8..38de3765ccc1b 100644 --- a/platform-includes/logs/usage/php.laravel.mdx +++ b/platform-includes/logs/usage/php.laravel.mdx @@ -9,7 +9,7 @@ Log::warning('User {id} failed to login.', ['id' => $user->id]); Log::error('This is an error message'); // Log directly to the Sentry channel -Log::channel('sentry')->error('This will only go to Sentry'); +Log::channel('sentry_logs')->error('This will only go to Sentry'); ``` You can pass additional attributes directly to the logging functions. These properties will be sent to Sentry, and can be searched from within the Logs UI, and even added to the Logs views as a dedicated column.