Hi guys! How do you configure spryker in docker to send the log from yves and zed directly to the st

URB1K7DEU

Hi guys! How do you configure spryker in docker to send the log from yves and zed directly to the stdout? They are directly sent to Kibana. I currently have:

$config[LogConstants::LOG_FILE_PATH_YVES] = '<php://stdout>';
$config[LogConstants::LOG_FILE_PATH_ZED] = '<php://stdout>';
$config[LogConstants::EXCEPTION_LOG_FILE_PATH_YVES] = '<php://stderr>';
$config[LogConstants::EXCEPTION_LOG_FILE_PATH_ZED] = '<php://stderr>';
$config[QueueConstants::QUEUE_WORKER_OUTPUT_FILE_NAME] = '<php://stdout>';

And in php-fpm I set:

php_admin_value[error_log] = /proc/self/fd/2

I see the errors in Zed, but not in Yves. Anyone has figured this out?

sprymiker

<php://stdout>

Won’t work at all. As php-fpm does not support proxying to /proc/self/fd/1.

So only /proc/self/fd/2 and <php://stderr> would work.

UQ958DA4U

We are using a Filebeat companion container for this.

UMZRJAE7M

we're using a file with symlink like nginx does in their official image:
https://docs.docker.com/config/containers/logging/

sprymiker

@UMZRJAE7M I would like to ask the details…

The problem I face is that php-fpm worker cannot access neither /proc/1/fd/2 or /dev/stderr. So symlink does not work.

UMZRJAE7M

@ULYHPR789 good to know - we wanted to switch to symlink because our solution is not that nice

current solution is that we create a fifo file that we use as log destination. In our entrypoint, we use:

mkfifo /var/log/stdout
chmod 666 /var/log/stdout

and in the Spryker config, we use /var/log/stdout as log destination

sprymiker

How do you create a link?

UMZRJAE7M

well, this solution is without link, that's why I said not so nice

sprymiker

Ok. How do you redirect /var/log/stdout into docker container output?

UMZRJAE7M

it's a fifo file. If I get it right, it's content is automatically posted into stdout

UMZRJAE7M

ah, we tail it via supervisord

command=tail -f /var/log/stdout

UMZRJAE7M

as I said, not that nice

sprymiker

Ok. That explains.

sprymiker

Symlink does not work. As worker has no permission to write into php-fpm process output.

UMZRJAE7M

thx for that information - I wanted to switch to symlink soon

sprymiker

However <php://stderr> works properly. The only thing to do is to set the following for php-fpm pool

catch_workers_output = yes
decorate_workers_output = no

sprymiker

At that point it works properly.

sprymiker

But console commands are different case. We are trying to find a way to redirect logs spawned by scheduled console commands (e.g. Jenkins) into container output.

UMZRJAE7M

that's still an open point in our setup

sprymiker

I will notify you about our solution when it becomes mature.

UMZRJAE7M

Maybe helpful link:
https://bugs.php.net/bug.php?id=71880

UMZRJAE7M

so in php 7.3 <php://stdout> should work

sprymiker

Yep. I’ve already mentioned the decorate_workers_output = no

So web requests are good. CLI is still not clear.