Use jira_ prefix when logging client responses
What does this MR do and why?
We introduced a new integrations log event emitted from a Jira API client in !101702 (merged).
These log events use generic keys that semantically conflict with top-level log events we emit through Rails, such as status
. When emitting sub-component log events, we should use key names that clearly disambiguate them from ordinary request logs (in Kibana, these will all appear in the same search index).
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.