You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a single request/response cycle it works fine, however that changes when you switch it to an Octane-based container which holds the code in memory, such as https://github.com/Anteris-Dev/docker-laravel-roadrunner . When it's running with the log channel set to a text file, it works as expected.
But when you switch it to GELF-based logging (e.g. Seq), only the first log entries are created once the framework has been cached on its first run. Any subsequent log entries fail to appear. It's like the connection isn't implicitly closed once the message has been sent via its transport.
To reproduce:
Create a POST endpoint which logs traffic and payload.
Establish a baseline by sending 10 looped POST requests to it, using FPM and text-based logging.
Switch to Seq logging and confirm the behaviour is identical (10 requests appearing in the event log).
Change to Octane-based PHP and repeat with text-based logging. Confirm it is identical.
Switch to Seq logging and watch in real time. Only the first POST will be logged.
Probably not a bug, but worth bringing up for the purposes of investigation. It's an excellent package and it would be great to combine it with the performance of Roadrunner and/or Swoole.
The text was updated successfully, but these errors were encountered:
I've been using this with the Laravel wrapper (https://github.com/hedii/laravel-gelf-logger) for a long while and it's been working flawlessly. It's working as a bridge to send log data from Laravel directly to Seq (https://datalust.co/).
Example configuration in
config/logging.php
:On a single request/response cycle it works fine, however that changes when you switch it to an Octane-based container which holds the code in memory, such as https://github.com/Anteris-Dev/docker-laravel-roadrunner . When it's running with the log channel set to a text file, it works as expected.
But when you switch it to GELF-based logging (e.g. Seq), only the first log entries are created once the framework has been cached on its first run. Any subsequent log entries fail to appear. It's like the connection isn't implicitly closed once the message has been sent via its transport.
To reproduce:
Probably not a bug, but worth bringing up for the purposes of investigation. It's an excellent package and it would be great to combine it with the performance of Roadrunner and/or Swoole.
The text was updated successfully, but these errors were encountered: