Refactor logging statements #6476
Description
What we’re after
There are quite a few places where we are using inefficient logging statements (.format instead of the inbuilt or f-strings) These are slower and should be changed.
Related ticket(s)
(Include the tickets that either came before, after, or are happening in tandem with this new ticket)
- [ ]
Action item(s)
(These are the smaller tasks that should happen in order to complete this work)
- [ ]
Completion criteria
(What does the end state look like - as long as this task(s) is done, this work is complete)
- [ ]
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)