We should log information about the id of analyzes that failed to be stored to be sure with tractability of issues. We already submit errors to Sentry, but we should be able to track down to specific analyzer what went wrong. For this purpose we should implement an exception handler (similar to the one in user-api https://github.com/thoth-station/user-api/blob/6ad7acc0ae99b47708466755542d5015e54b8b77/thoth_user_api/entrypoint.py#L105-L116) that states exact time when the exception happened in the cluster as well as additional info such as analysis id that submitted results.
We should log information about the id of analyzes that failed to be stored to be sure with tractability of issues. We already submit errors to Sentry, but we should be able to track down to specific analyzer what went wrong. For this purpose we should implement an exception handler (similar to the one in user-api https://github.com/thoth-station/user-api/blob/6ad7acc0ae99b47708466755542d5015e54b8b77/thoth_user_api/entrypoint.py#L105-L116) that states exact time when the exception happened in the cluster as well as additional info such as analysis id that submitted results.