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
Currently all the logs from everywhere is written into one big log stdout.
It's hard to figure out how is each diagnosis is doing for individual app, and even harder to see when an API failure happened as it's burried in this big log.
With more and more features we're adding, I think we should have a strategy how we improve our logging so we have more visibility what's going on.
My initial suggestion is to only log to stdout API errors, and all analyzer data science work we can create a separate log per job, and have a internal UI like what we've done for deployer to show each job's specific log.
The text was updated successfully, but these errors were encountered:
Currently all the logs from everywhere is written into one big log stdout.
It's hard to figure out how is each diagnosis is doing for individual app, and even harder to see when an API failure happened as it's burried in this big log.
With more and more features we're adding, I think we should have a strategy how we improve our logging so we have more visibility what's going on.
My initial suggestion is to only log to stdout API errors, and all analyzer data science work we can create a separate log per job, and have a internal UI like what we've done for deployer to show each job's specific log.
The text was updated successfully, but these errors were encountered: