[PRM-696] Add logging to ODS API service call to support debugging of potential ODS API issue#1090
Conversation
… potential ODS API issue
chrisbloe
temporarily deployed
to
development
GitHub Actions
Inactive
adamwhitingnhs
approved these changes
Feb 13, 2026
chrisbloe
temporarily deployed
to
development
GitHub Actions
Inactive
Code security issues foundView full details here. |
NogaNHS
approved these changes
Feb 16, 2026
steph-torres-nhs
approved these changes
Feb 16, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Jira ticket: PRM-696
Description
Some new logging is being added to help us see how long some API calls are taking.
Context
We have seen some slow behaviour recently and would like to add some logging to assist diagnosing the problem.
Checklist
Tasks for all changes:
I have run git pre-commits.(WIP)I have successfully deployed this change to a sandbox and witnessed unit and e2e tests passing:Deploy - Sandbox- workflow run - TBCSANDBOX Full- Deploy feature branch to sandbox- workflow run - TBC