APPEALS-29120 - Enhance hlr_sync_lock with logging

[Jruuuu]

Resolves APPEALS-29120

Description

enhance the hlr_sync_lock with logging of creation and releasing of hlr_sync_lock key and errors when they occur

Acceptance Criteria

• add logging for lock creation
• add logging for lock release
• add logging for error
• add logging error to rspec

Testing Plan

1. Test Plan: APPEALS-29165
2. Test Execution: APPEALS-29251

Tests

Test Coverage

Did you include any test coverage for your code? Check below:

• RSpec
• Jest
• Other

Code Climate

Your code does not add any new code climate offenses? If so why?

• No new code climate issues added

Logging

• Are logs being produced at appropriate log levels (debug, info, warn, error, fatal)? yes, these errors will not be sent to raven but will be logged via Rails Logger
• Are logs structured (e.g., using log tags) for easier querying and analysis?
• Are sensitive data (e.g., passwords, tokens) redacted or omitted from logs?
• Is log retention and rotation configured correctly?
• Are logs being forwarded to a centralized logging system if needed?

Error Handling

• Are errors being caught and handled gracefully? yes
• Are appropriate error messages being displayed to users?
• Are critical errors being reported to an error tracking system (e.g., Sentry, ELK)?
• Are unhandled exceptions being caught at the application level ?

[codeclimate]

Code Climate has analyzed commit 305faeb and detected 0 issues on this pull request.

View more on Code Climate.

[jtsangVA]

lgtm