All geek questions in one place

What do you think about saving the stack trace in a special log table?

Suppose you have a special log table for your application.

What do you think of creating a BLOB field for a possible stack trace?

Logging is also performed for the file, but it is not so convenient to read a text file, moreover, the database is more "accessible".

+3
source share
4 answers

... , . . , / , . . , , - Splunk, , , .

+4

, - ? . , , , ssh.

+4

, , , , , , .

, , , ; , , , , , , .

+1

? , , , Blob?

If I implemented something like this, I would split the exceptions into separate StackTraceElements and save them in the correct table. Over time and many failures, you can create interesting statistics about the nature of risk and quality in your application.

+1
source

Source: https://habr.com/ru/post/1742806/

More articles:


All Articles