When an error happens on the server, all the client gets is the exception message. Many times that is enough, as the user can use the exception message to search the server logs, but sometimes the server logs are not available, and changing the server logging configuration is not always an option.

We don't want to fill the client logs with too server stack traces either, so we need to limit the amount of information we send with one or more of

1. Disable server stack traces by default, and add a client configuration property to request stack traces when enabled.
2. Don't send the full stack trace, just 5-10 stack frames (for each exception, if there's an exception chain).
3. Don't send the stack trace for common exceptions like IllegalLifecycleStateException.