I am searching for the easiest method to keep stacktrace (acquired via Thread.dumpStack()) and exception trace within the database.

I am developing an application that does application performance. It traces method calls(with duration), captures errors (that lead to exception trace) &lifier creates stack trace for slow accomplishments.

The atmosphere is Java + MySQL 5.

Presently, the trace info of the web request &lifier stack traces are saved inside a file(as json) and meta information is saved within the database table.

For confirming &lifier replication purpose, I am considering storing them within the database. With an average, how big complete trace info is 40 kb. Could it be prudent to keep them within the db or ensure that it stays within the file system and proceed to nosql.

Moving to nosql, i'm able to solve the replication but nonetheless the confirming is a tough one.