Improve logging in the postprocessing service

[kobergj]

Description

User Stories

The postprocessing service is the center piece of uploads in ocis. Unfortunately logging is scarce. We need to improve logging so we can easily trace failing uploads

Acceptance Criteria

• log each incoming event (debug level)
• log events that instruct the service to retry an event on info level
• log errors it encounters on error level
• log postprocessing restart events
• log the outcome of all operations even if they were successful
• make sure all postprocessing steps are tracked in the logs

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues
• Configuration changes
  • The next branch of the ocis charts is compatible