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
Please answer these questions before submitting your issue.
What did you do? If possible, provide a simple script for reproducing the error.
We have Swoole applications in docker running on multiple servers, sending logs to a central server via syslog.
We are having issues with grouping multiple core Swoole errors error lines in one line.
For example: if the function deadlock_check() would have a few spaces, it would make grouping and parsing those logs allot easier.
Current:
echo "\n===================================================================",
"\n [FATAL ERROR]: all coroutines (count: {$count}) are asleep - deadlock!",
"\n "; # << add a space
// "\n ===================================================================\n";
...
echo "\n [Coroutine-{$cid}]";
echo "\n --------------------------------------------------------------------\n"; # << prefix with a space
echo Coroutine::printBackTrace($cid, DEBUG_BACKTRACE_IGNORE_ARGS, $depth); # << prefix with a spaces
echo "\n "; # << prefix with a space
And this should probably be the case for all logs that act as a unit, including Swoole crash logs and so on.
The text was updated successfully, but these errors were encountered:
Please answer these questions before submitting your issue.
We have
Swoole
applications indocker
running on multiple servers, sending logs to a central server viasyslog
.We are having issues with grouping multiple core Swoole errors error lines in one line.
For example: if the
function deadlock_check()
would have a few spaces, it would make grouping and parsing those logs allot easier.Current:
Suggestion:
And this should probably be the case for all logs that act as a unit, including Swoole crash logs and so on.
The text was updated successfully, but these errors were encountered: