updated sentry config

config/sentry.php

@@ -14,6 +14,12 @@ return [
         // Capture Laravel logs in breadcrumbs
         'logs' => env('SENTRY_BREADCRUMBS_LOGS', true),
 
+        // Capture Laravel cache events in breadcrumbs
+        'cache' => env('SENTRY_BREADCRUMBS_CACHE', true),
+
+        // Capture Livewire components in breadcrumbs
+        'livewire' => env('SENTRY_BREADCRUMBS_LIVEWIRE', true),
+
         // Capture SQL queries in breadcrumbs
         'sql_queries' => env('SENTRY_BREADCRUMBS_SQL_QUERIES', true),
 
@@ -43,9 +49,18 @@ return [
         // Capture views as spans
         'views' => env('SENTRY_TRACE_VIEWS', true),
 
+        // Capture Livewire components as spans
+        'livewire' => env('SENTRY_TRACE_LIVEWIRE', true),
+
         // Capture HTTP client requests as spans
         'http_client_requests' => env('SENTRY_TRACE_HTTP_CLIENT_REQUESTS', true),
 
+        // Capture Redis operations as spans (this enables Redis events in Laravel)
+        'redis_commands' => env('SENTRY_TRACE_REDIS_COMMANDS', false),
+
+        // Try to find out where the Redis command originated from and add it to the command spans
+        'redis_origin' => env('SENTRY_TRACE_REDIS_ORIGIN', true),
+
         // Indicates if the tracing integrations supplied by Sentry should be loaded
         'default_integrations' => env('SENTRY_TRACE_DEFAULT_INTEGRATIONS', true),