Context:
When the same error occurs a lot of times in a short amount of time, the logging truncates the stracktraces to prevent an overflow of the logs. in general, that's fine but an additional hint should be printed that states that the stacktrace has been truncated.

AT:

• whenever the stacktrace is being truncated in the Optimize logs there's an additional log stating that this is due to prevent an overflow of the logs and that the user can just have a look at the beginning of the log to see the actual stacktrace