Is storing stack traces in database recommended?

The current system I am working on goes through a set of documents & performs some logic using the metadata of the document. If the metadata of a document is throws an exception. The system logs the exception, fail the job & let the developer fix the issue by looking at logs before moving on.

I want to improvise this system by making system fault tolerant as I have seen that generally the job fails because of few documents. System continues even if there's an exception raised. The exception information would be stored in the database table along with document information. This information would be sent to developer who can then work on fixing it without having customer waiting. The customer can later process those failed documents separately.

My question is how to store the exception information in table. The exception would already be logged in the log file. One idea I was thinking was to store the time stamp of the exception so that developer can later find the time stamp in log file and understand the exception. But this comes with a possibility that the log files might be deleted.

Does it make sense to store the entire stack trace in the database?


It is not uncommon to see production systems log errors and exceptions to an errorlog table in either the same database or separate one, time stamp , userid and the exception and stack are converted into a string and stored in a column that is defined as varchar(3000) or a value that will store enough of your exception info

Need Your Help

Is it possible to translate an ImageView on the android platform using Picasso?

android picasso

For example, if I loaded an image into an ImageView as such:

"Direct link to any fancybox", but with URL in address bar

jquery url hyperlink fancybox address-bar

I took a look at this post How to create a direct link to any fancybox box and I managed to implement it. However, I noticed that whenever someone clicks an image, the URL doesn't change. So, basic...