monolog | Sends your logs to files , sockets , inboxes , databases | Socket library

I have downgraded a Symfony 5.2 app template to use Symfony 4.4 in order to allow the use of some libraries that require an older version of Symfony. The problem is that when I do composer install, I get this error near the end of the installation:

sh: symfony-cmd: command not found

It seems that the installations are mostly successful, as my vendor folder is created and populated. But I'm worried about the error.

What does this error mean? How do I fix it?

====

Edit: Here's my composer.json file:

I've created Lumen Passport in my local and free Heroku and successfully created it. Now I’m creating my production lumen in digital ocean VPS. All of my applications work fine and give good bad responses format when it should be failed responses, except my login. In my login, it passes a good response when correct emails and passwords but returns 500 in other cases.

This is my code in my LoginService.php

I updated my composer.json file to reflect the 6.0.* changes, and ran my composer update "symfony/*" code, and it returned this:

I am trying to create custom log in laravel and i am using monlog\LineFormatter class to formatt my final log

I have a Symfony 5.3 application. When the container is compiled, the following file appears:

var/cache/dev/App_KernelDevDebugContainerDeprecations.log

In contains a serialized list of deprecation messages:

I'm a beginner in Symfony and would like to know how to deal with the following installation issue: I'm using Symfony 4.4 and trying to install Swift Mailer. Following the documentation on this link, when I ran the following command composer require symfony/swiftmailer-bundle , I got this error message:

Your requirements could not be resolved to an installable set of packages.

Problem 1

• symfony/web-server-bundle is locked to version v4.4.0 and an update of this package was not requested.
• symfony/web-server-bundle v4.4.0 requires php ^7.1.3 -> your php version (8.0.12) does not satisfy that requirement.

Problem 2

• laminas/laminas-code 3.4.1 requires php ^7.1 -> your php version (8.0.12) does not satisfy that requirement.
• symfony/proxy-manager-bridge v4.4.34 requires friendsofphp/proxy-manager-lts ^1.0.2 -> satisfiable by friendsofphp/proxy-manager-lts[v1.0.5].
• friendsofphp/proxy-manager-lts v1.0.5 requires laminas/laminas-code ~3.4.1|^4.0 -> satisfiable by laminas/laminas-code[3.4.1].
• symfony/proxy-manager-bridge is locked to version v4.4.34 and an update of this package was not requested.

Any idea how to handle that?

Update:

This is my composer.json file:

I am using Eloquent for database calls with slim framework here is my composer.json

Is it recommended to ship logs directly from a PHP app to ElasticSearch? Or is it always better to store to file and use filebeat to ship the logs? I'm familiar with C# and Serilog implementation sending directly to ES and we've never had an issue with it, but was wondering if the same could be done with a PHP app using Monolog without performance being severely impacted. I'm assuming Serilog is able to asynchronously send the logs, I'm not sure if the Monolog implementation on PHP is able to do that or if it would only be OK to ship directly as long as they're infrequent error logs but info/debug logging would cripple performance. Anybody have any experience doing this? For additional background, we'd be using AWS OpenSearch and the PHP app would also be running at AWS in ECS/Fargate containers, so it would be inside the same network.

Laravel console exception output uses nunomaduro/collision package, which seems to merge the exception and all chained exception stack traces into one incredibly useful output.

Laravel log output however uses Monolog, which doesn't appear to do this by default, and only appears to output the stack trace of the last exception thrown. It will output the messages of the previous exceptions, but not the stack traces.

When using an exception methodology which catches an exception, creates a new exception adding more contextual information and attaching the previous one to it, creating a chain of exceptions. Having the stack trace of only the last exception thrown isn't particularly useful.

The first exception thrown (last one in the chain) is the original cause of the error, all of the other exceptions are simply adding context/information to it.

Is there a way to get Laravel to merge the stack traces of each exception in the chain?

Failing that, is there a way to just get Laravel/Monolog to output the stack trace of the first exception thrown (the last one in the chain), instead of the last exception thrown (the first one in the chain)?

(Very contrived) code example: