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

Move debug logs to new file #112

Open
jewzaam opened this issue Apr 30, 2015 · 1 comment
Open

Move debug logs to new file #112

jewzaam opened this issue Apr 30, 2015 · 1 comment

Comments

@jewzaam
Copy link
Member

jewzaam commented Apr 30, 2015

So it can be indexed differently than server.log, or not indexed at all. This would allow us to log anything in the request and response. It's not going to be useful in a managed environment unless it is indexed, though, so we'll have to work through how best to do that.

I was going to remove a bunch of debug statements from MongoCRUDController but there really seems to be value with those.

Maybe we could have a separate location for these that is controlled by puppet. Then in dev we can dump them to server.log so they get sucked into splunk. But in non-dev we have it go to /dev/null?

@bserdar
Copy link
Contributor

bserdar commented Apr 30, 2015

Yes pls don't remove debug level logs. They are valueble for debugging, as
the name implies.

On Thu, Apr 30, 2015 at 7:27 AM, Naveen Malik [email protected]
wrote:

So it can be indexed differently than server.log, or not indexed at all.
This would allow us to log anything in the request and response. It's not
going to be useful in a managed environment unless it is indexed, though,
so we'll have to work through how best to do that.

I was going to remove a bunch of debug statements from MongoCRUDController
but there really seems to be value with those.

Maybe we could have a separate location for these that is controlled by
puppet. Then in dev we can dump them to server.log so they get sucked into
splunk. But in non-dev we have it go to /dev/null?


Reply to this email directly or view it on GitHub
#112.

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

No branches or pull requests

2 participants