<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=342726) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=342726) </details> <!--IssueSummary end--> As seen in #341974 it would be beneficial to log info about API calls before we make them in case the far end(GitHub) times out or throws a different exception through octokit. See [this suggestion](https://gitlab.com/gitlab-org/gitlab/-/issues/341974#note_696529977) about `github_identifiers` as a possible thing to augment areas like [this](https://gitlab.com/gitlab-org/gitlab/blob/228e7ddd3fbae04bfb17c85ec3893c239b9e7f36/lib/gitlab/github_import/importer/pull_requests_merged_by_importer.rb#L39-39) with(any line before we reach out to GitHub's octokit that calls an API would be helpful). Related to #341974.