krallin
commented
4 years ago Supercronic captures your logging and adds a little bit of context around it, but I understand this isn't desirable if your comand already outputs structured logging. You'll be able to turn that off as of #67, which adds a -passthrough-logs flag to avoid decorating your logs. #67 also adds a -quiet flag to remove informational messages (I really think turning using that is a bad idea, since it'll make it harder to understand if your command isn't running, but that's up to you).
berkankisaoglu
fancyremarker
Hi. Thanks for this beautiful package.
We are seeing an extra line of unnecessary log whenever our log received. For example:
Feb 12 05:36:15 5c1e5dd859a6 test-cron time="2020-02-12T13:36:10Z" level=info channel=stderr iteration=56 job.command="php artisan test:test" job.position=6 job.schedule="30 */2 * * *"Feb 12 05:36:15 5c1e5dd859a6 test-cron time="2020-02-12T13:36:10Z" level=info msg="message content here " channel=stderr iteration=56 job.command="php artisan test:test" job.position=6 job.schedule="30 */2 * * *"Here, second log record is legit, but the first one is not created by us (there is no
msgfield in the first log). And we are seeing logs like the first one here for every log that we recorded.This results in too much logging space.
Is there any configuration we are missing and/or misusing?
By the way, we are using v0.1.5.
Thanks!