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.

Sign up for GitHub

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

Jump to bottom

Log in syslog #61

Open
rafaeljusto opened this issue Mar 12, 2014 · 3 comments
Open

Log in syslog #61

rafaeljusto opened this issue Mar 12, 2014 · 3 comments
Assignees
@rafaeljusto
Labels
enhancement ready

Comments

@rafaeljusto
Copy link
Owner

Allow sending the log to a remote location. This is good when we have many modules in different servers logging and want to keep all of them in only one place.
@rafaeljusto rafaeljusto self-assigned this Mar 12, 2014
@rafaeljusto
Copy link
Owner Author

Our log could also log the file and line that reported the message.
http://golang.org/pkg/log/#Logger.Output

@rafaeljusto
Copy link
Owner Author

The correct way to log the file and the line is
http://golang.org/pkg/runtime/#Caller

@rafaeljusto
Copy link
Owner Author

See #100

@rafaeljusto rafaeljusto mentioned this issue Sep 10, 2014
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafaeljusto rafaeljusto

Labels
enhancement ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rafaeljusto