Closed gregclarity closed 1 year ago
Just found this package and started to using it today and nothing seems to be working. No logs in CW. However, if I unintentionally make a non-existing command like a wrong spelling of some sort, the error gets logged to CW like php artisan optimize:something.
@gregclarity
I used composer require pagevamp/laravel-cloudwatch-logs:1.1.1
to update my dependencies and it worked fine. How did you pull latest version?
@prezire
make a non-existing command like a wrong spelling of some sort, the error gets logged to CW like php artisan optimize:something.
I think this is intended.
nothing seems to be working
this is not. What log level did you used in your code and your configuration?
Initially I just did a composer update and it pulled down the latest version (1.1.1).
Just now I did a composer require pagevamp/laravel-cloudwatch-logs:1.1.1 as suggested, and then another composer update after. Nothing was downloaded/updated.
As far as log-levels go, we are logging everything, min_log_level=debug
It should be noted that when I switch to the daily LOG_CHANNEL I get the normal logs that I'd expect.
same here, no log group gets created although both the task role and task execution role have the correct permissions.
FYI: I'm on laravel ^9.0
Same vibes here.
I got this error after try v1.1.1
`[2023-09-04 20:43:58] laravel.EMERGENCY: Unable to create configured logger. Using emergency logger. {"exception":"[object] (Error(code: 0): Class \"PhpNexus\Cwh\Handler\CloudWatch\" not found at /opt/project/vendor/pagevamp/laravel-cloudwatch-logs/src/Logger.php:34) [stacktrace]
"} `
Hi guys, Change line "pagevamp/laravel-cloudwatch-logs":"^1.0" on composer.json to "pagevamp/laravel-cloudwatch-logs": "1.0.3". Remove composer.lock and folder vendor. Run command composer install
Success!
Version 1.1.1 doesn't work with Laravel version lower than 10, my bad. Lock your version to 1.0.3 for Laravel 9 and below according to @vanessasoutoc .
Thanks @vanessasoutoc .
Awesome. Thanks for the info. I rolled back to 1.0.3 and we're back to logging correctly.
Thankfully I'll be upgrading us to laravel 10.x soon so I won't have to be using old code for long.
We pushed updates to all of our deployments yesterday and all of a sudden cloudwatch logging quit working. No errors, nothing amiss on the frontend, just logs stopped showing up in CW.
I went looking and found this ticket, then did a composer update... I pulled the latest version of this dependency 1.1.1, and verified the fixes outlined here are in my vendor dir...
I also tried the workaround written above and still no logs. Any help would be greatly appreciated on this as we've got some production clients running on this.
Originally posted by @gregclarity in https://github.com/pagevamp/laravel-cloudwatch-logs/issues/43#issuecomment-1700152838