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

Better logging options #105

Closed
mitchellh opened this issue May 2, 2014 · 3 comments
Closed

Better logging options #105

mitchellh opened this issue May 2, 2014 · 3 comments
Labels
type/enhancement Proposed improvement or new feature

Comments

@mitchellh
Copy link
Contributor

Originally reported by @blalor

We need to provide better options for logging that isn't geared towards humans. I think this should probably entail both syslog and a file option.

@blalor
Copy link
Contributor

blalor commented May 2, 2014

Ideally there'd be an option for outputting structured messages via JSON, including timestamp, level, component, etc.

@mitchellh
Copy link
Contributor Author

We use a pretty machine-friendly format. The truth is, internally we only get them as a string as well (with a timestamp), no component, nothing. Just a string.

We leave the parsing of the logs up to logstash or some higher level citizen.

@armon armon closed this as completed in 0836a22 May 21, 2014
@carlivar
Copy link

I think this should probably entail both syslog and a file option.

This is technically only half completed, since it requests both syslog and file. I'll file another issue about file logging though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Proposed improvement or new feature
Projects
None yet
Development

No branches or pull requests

3 participants