<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=299311) </details> <!--IssueSummary end--> ### Proposal Currently BulkImports is using `Gitlab::ErrorTracker` to track exceptions. This is great, but it only logs to the `exceptions.log` file. Since most of the import process is logged within the `imports.log`, I propose to create a `Gitlab::Import::ErrorTracker` that log to both `exceptions.log` and `imports.log`. This will make debugging and following a import process easier.