Two methods to achieve error record

Software bugs are inevitable. How can we record software errors so that we can easily find problems and not confuse customers?

Sometimes you call a customer to ask what they only say and operate, and then there is a problem. There are no more details to tell you, and you can find problems through your intuition.

There was a solution that I always thought was good. It took time to implement it again.

Error Reporting Server

Run thisProgram, Used to accept error reports

 

Run the client. If an exception is thrown, the client application encounters an exception.

View the server again

I clicked three times and sent three abnormal reports to the server.

There are three image files under the directory corresponding to the server, which is the interface for client exceptions. Through this interface, you can collect user operation time and track problems.

Data reports can be directly written to the database server.

 

For ASP. NET applications, my method is to generate a log directory. If an exception occurs, the system records the exceptions in days, such

The system will be abnormal every few days. It seems that my programming technology is a little bad. So many exceptions.

Sometimes the user is not operating properly, but the user is not prompted, but is recorded in the exception log. The user does not see it, and the log does not play much role on the programmer, but it is an improper operation.

For example, if the item name cannot exceed 50 ASCII characters and 52 characters are entered, an exception is reported. This is a design issue and is done well. When a user inputs an error, the system prompts the input error instead of recording the error.

 

To build a software program, you must be careful. You can also see the programmer's attitude towards program execution from the method of error reporting.

Sometimes it is not an error. It cannot be regarded as an exception. In this case, our program did not take it into consideration.