You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
The text was updated successfully, but these errors were encountered: