Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve analyzer logging situation #68

Open
tnachen opened this issue Dec 24, 2017 · 2 comments
Open

Improve analyzer logging situation #68

tnachen opened this issue Dec 24, 2017 · 2 comments

Comments

@tnachen
Copy link
Contributor

tnachen commented Dec 24, 2017

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.

@tnachen
Copy link
Contributor Author

tnachen commented Jan 3, 2018

@xiaoyzhu @cherplunk thoughts?

@xiaoyzhu
Copy link
Contributor

xiaoyzhu commented Jan 3, 2018

For now I think writing all the diagnosis output to a separate log file for each app can be useful. Cherrie is working on a change to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants