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
Hi all, this is a really weird behavior I start noticing. The logs from my cloud run instances suddently stop appearing in the Cloud Logging view (using dd-trace 4.16.0 and serverless-init 1.1.1)
Its weird because when I restart the instance the logs start appearing again without any issue, but after some hours new logs are never shown until I restart the instance again.
I even try console.log (am using Node 18) for every request inside the instance to test, but even that log dissapear.
I've been debugging this behavior for almost a week, and recently try to remove everything form datadog and the logs never dissapear again.
Maybe something happend in the newer version of dd-trace or the newer version of the serverless-init image that all of the sudden starts "eating" the logs made to stdout.
Some images to show the behavior, the first is when everything works, the logs are showing up on the stackdriver panel:
After sometime, the logs made from my instance never appear again, only showing the default Cloud Run request log:
Here are the env variables that my cloud run is using:
Hi all, this is a really weird behavior I start noticing. The logs from my cloud run instances suddently stop appearing in the Cloud Logging view (using dd-trace 4.16.0 and serverless-init 1.1.1)
Its weird because when I restart the instance the logs start appearing again without any issue, but after some hours new logs are never shown until I restart the instance again.
I even try
console.log
(am using Node 18) for every request inside the instance to test, but even that log dissapear.I've been debugging this behavior for almost a week, and recently try to remove everything form datadog and the logs never dissapear again.
Maybe something happend in the newer version of dd-trace or the newer version of the serverless-init image that all of the sudden starts "eating" the logs made to stdout.
Some images to show the behavior, the first is when everything works, the logs are showing up on the stackdriver panel:
After sometime, the logs made from my instance never appear again, only showing the default Cloud Run request log:
Here are the env variables that my cloud run is using:
Thanks for any help!
The text was updated successfully, but these errors were encountered: