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

User Story: Logging #40

Open
zeitlerc opened this issue Jan 19, 2016 · 1 comment
Open

User Story: Logging #40

zeitlerc opened this issue Jan 19, 2016 · 1 comment

Comments

@zeitlerc
Copy link
Collaborator

As a developer (or site administrator), I want the application to have some logging implemented, so that myself and others can debug production issues.

Scenario: Logging 500 Errors
Given that the application is up and running,
When a fatal exception occurs to cause a 500 error,
Then the error is logged for someone to review

Original comment:
Add file logging to the application so that issues in the production can be debugged without impacting the application. Logging libraries typically allow logging level settings, so log messages can be grouped by severity. One consideration should be rotating the log file daily or weekly so no single log file becomes too large.

@atquail
Copy link
Collaborator

atquail commented Jan 19, 2016

@zeitlerc , we are going to prioritize this into our Release 1 backlog with the assumption that the initial implementation will be simple to start. Also as an FYI, I am going to re-write your original comment to include a story narrative from the perspective of a developer and add in a test scenario.

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

3 participants