Handlers ======== ElasticsearchLogstashHandler ---------------------------- This handler deals directly with the HTTP interface of Elasticsearch. This means it will slow down your application if Elasticsearch takes times to answer. Even if all HTTP calls are done asynchronously. In a development environment, it's fine to keep the default configuration: for each log, an HTTP request will be made to push the log to Elasticsearch. In a production environment, it's highly recommended to wrap this handler in a handler with buffering capabilities (like the ``FingersCrossedHandler`` or ``BufferHandler``) in order to call Elasticsearch only once with a bulk push. For even better performance and fault tolerance, a proper `ELK stack`_ is recommended. To use it, declare it as a service: .. configuration-block:: .. code-block:: yaml # config/services.yaml services: Symfony\Bridge\Monolog\Handler\ElasticsearchLogstashHandler: ~ .. code-block:: xml .. code-block:: php // config/services.php use Symfony\Bridge\Monolog\Handler\ElasticsearchLogstashHandler; $container->register(ElasticsearchLogstashHandler::class); Then reference it in the Monolog configuration: .. configuration-block:: .. code-block:: yaml # config/packages/prod/monolog.yaml monolog: handlers: es: type: service id: Symfony\Bridge\Monolog\Handler\ElasticsearchLogstashHandler .. code-block:: xml .. code-block:: php // config/packages/prod/monolog.php use Symfony\Bridge\Monolog\Handler\ElasticsearchLogstashHandler; $container->loadFromExtension('monolog', [ 'handlers' => [ 'es' => [ 'type' => 'service', 'id' => ElasticsearchLogstashHandler::class, ], ], ]); .. _`ELK stack`: https://www.elastic.co/what-is/elk-stack