Errors

It is a good idea to send errors in production environment to error log. Errors may contain sensitive information. Even so errors maybe helpful to development team or to QA team, errors need to be suppressed in production environment for viewing by everyone. Errors are good way to troubleshoot an issue therefore only trusted people can have access to this information. If not a trusted person get an access to this information, this information maybe used against the company and for a personal benefit.

What to do in a case when there are more servers than one? Even so it is possible to inspect the log files in a single server, however it is impossible to do so when there is more than one server is available and web traffic is redirected to a different server each time.

Log aggregation is needed in this case. All of the logs will be send to a central location.

Logs may contain sensitive information. Please consult your company lawyer of how long logs can be stored, because logs can be used against your company in a lawsuit.

Not all of the errors have the same severity level nor they have same level of occurrence, therefore it makes sense to prioritize errors by their likelihood and severity.

Ranking system should be in place to fix errors.

When an error is fixed, there should be a way to validate that the fix really fixed that error and that error will not happen again.