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

refactor logging to include the time #33

Closed
ben-jones opened this issue Sep 15, 2014 · 14 comments
Closed

refactor logging to include the time #33

ben-jones opened this issue Sep 15, 2014 · 14 comments
Milestone

Comments

@ben-jones
Copy link
Contributor

No description provided.

@ben-jones ben-jones added this to the Alpha release milestone Sep 15, 2014
@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

Not sure about this. Leaking PII maybe? (if we want to send logs back. otherwise fine with me)

@ben-jones
Copy link
Contributor Author

hmm. That's true, but it can be hard to determine what is happening if the logs don't include a timestamp. Also, timing in the logs will be dependent upon the scheduling server, so I'm unsure what additional info this would leak. @gsathya, thoughts?

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

This is as easy as changing the log format to "%(asctime)s: %(levelname)s: %(message)s"

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

I vote for including this and not sending back logs at all. I dislike the idea of sending back logs without user action.

@ben-jones
Copy link
Contributor Author

@gsathya, I know. I already added this for the vpn stuff. I just wanted to get people's thoughts on the change.

@ben-jones
Copy link
Contributor Author

@gsathya, why don't we make a separate command line arg for syncing logs so that users have the ability to send logs back, but we don't enable it by default. This may make some troubleshooting easier, but I am also ok with forcing users to copy the logs into an email or something.

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

@gsathya, why don't we make a separate command line arg for syncing logs so that users have the ability to send logs back, but we don't enable it by default.

I have strong feelings against this.

This may make some troubleshooting easier, but I am also ok with forcing users to copy the logs into an email or something.

This is the way to go.

@ben-jones
Copy link
Contributor Author

@gsathya, then I think this is the issue for you. Let's expand the issue to include adding time stamps, creating a wiki page for users to copy and submit their logs, and removing all of the log submission functionality.

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

Let's expand the issue to include adding time stamps,

#34

and removing all of the log submission functionality.

iclab/centinel-server#1

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

The PRs in #33 (comment) fix the issue. Closing the ticket.

@gsathya gsathya closed this as completed Sep 15, 2014
@ben-jones
Copy link
Contributor Author

@gsatha, we also need to add a wiki page describing to users how to submit logs. Do you want a separate issue for that for should that be this issue?=

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

Do we need this now? I'd rather have them create issues on GitHub

@gsathya
Copy link
Contributor

gsathya commented Sep 15, 2014

we also need to add a wiki page describing to users how to submit logs. Do you want a separate issue for that for should that be this issue?=

https://github.com/iclab/centinel/wiki/FAQ#faq

@ben-jones
Copy link
Contributor Author

@gsathya, seems fine.

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