Laravel日志能否绕过Filebeat与Logstash直接写入Elasticsearch？

Absolutely you can skip Filebeat and Logstash and send Laravel logs straight to Elasticsearch—no middleman required. Here are the two most reliable ways to pull this off:

Option 1: Use Laravel's Native Monolog Integration #

Laravel relies on Monolog under the hood, which comes with a built-in ElasticsearchHandler that lets you send logs directly to Elasticsearch. Here's how to set it up:

1. First, install the official Elasticsearch PHP client via Composer:

   composer require elastic/elasticsearch
   

2. Open config/logging.php and add a new log channel configuration:

   'elasticsearch' => [
       'driver' => 'monolog',
       'handler' => Monolog\Handler\ElasticsearchHandler::class,
       'with' => [
           'client' => Elastic\Elasticsearch\ClientBuilder::create()
               ->setHosts(['http://your-es-host:9200'])
               // Uncomment if your ES instance uses basic authentication
               // ->setBasicAuth('your-username', 'your-password')
               ->build(),
           'options' => [
               'index' => 'laravel-logs-' . date('Y-m-d'), // Daily rotating index for easier management
               'document_type' => '_doc', // Only needed for ES < 7.x; safely omit for 7+ versions
           ],
       ],
       'level' => 'debug', // Minimum log level to send to Elasticsearch
   ],
   

3. Set this as your default log channel (update the default value in config/logging.php) or call it explicitly in your code when needed:

   Log::channel('elasticsearch')->info('User completed checkout', ['user_id' => auth()->id(), 'order_total' => 99.99]);
   

Option 2: Use a Community Package #

If you prefer a more streamlined, low-boilerplate setup, community packages like spatie/laravel-elasticsearch-logger simplify the configuration process. Here's a quick walkthrough:

1. Install the package via Composer:

   composer require spatie/laravel-elasticsearch-logger
   

2. Add the Elasticsearch channel to config/logging.php:

   'elasticsearch' => [
       'driver' => 'elasticsearch',
       'hosts' => ['http://your-es-host:9200'],
       'index' => 'laravel-logs',
       'level' => 'debug',
       // Optional: Add auth credentials or additional client settings here
   ],
   

A Quick Note on Tradeoffs #

Direct integration works perfectly for smaller apps or low-traffic environments, but it’s worth remembering the advantages of tools like Filebeat/Logstash:

• They buffer logs during Elasticsearch outages, preventing data loss
• They handle log parsing, filtering, and transformation before sending to ES
• They reduce load on your Laravel app server by offloading log processing tasks

For high-traffic applications, you might still want to stick with the Filebeat/Logstash pipeline. But for most use cases, direct Elasticsearch logging from Laravel is totally feasible and straightforward.

内容的提问来源于stack exchange，提问作者Pratik Vanjare