Add stacktraces to error logs

[xtreding]

Problem

Jitsu writes error logs without a stack trace. It means that you can find a problem by error log message, but it can be inconvenient in the case of two similar log messages. This problem is solved by adding stack traces to error log messages. It will help to speed up the error localization process. The next problem is to identify errors. Jitsu should know all errors and give them IDs. IDs should be 10-15symbols strings that describe the error.

Solution

• [ ] - Error log messages should contain stack traces like:

Error: [${ERROR_IDENTIFIER}] a error message here which describes the case
 at main.func1()
	main.go:31
 at main.func0()
	main.go:10
 at main.main()
	main.go:5

• [ ] - Add identifiers to all errors and place them in one package. Use preconfigured errors in the whole project.