Conversation
32bdd4a to
714a2eb
Compare
2854009 to
05ab289
Compare
delta_backend/tests/test_delta.py
Outdated
| # Assert | ||
| self.assertFalse(result) | ||
| self.assertEqual(mock_table.put_item.call_count, 3) | ||
| self.assertEqual(self.mock_firehose_logger.send_log.call_count, 2) |
There was a problem hiding this comment.
Do you know any reason why we don't log errors processing an individual record to firehose, only successes or failures in the overall Lambda handler?
There was a problem hiding this comment.
Secondary question I suppose is why we're logging to Firehose at all when we're also logging to CloudWatch, but that's definitely one for another ticket
There was a problem hiding this comment.
Firehose seems superfluous. The Data is already sent to DLQ and is logged to cloudwatch. TBH I dont know why it is there.
It also sends the error to firehose in the handler exception. If firehose has an issue, we will have an unhandled exception
Perhaps we need a ticket to look at refactoring with these comments
There was a problem hiding this comment.
ticket raised https://nhsd-jira.digital.nhs.uk/browse/VED-301
There was a problem hiding this comment.
As discussed - the logging change was introduced in this PR so let's fix that now. The investigation into why we're logging to Firehose can come later 👍
There was a problem hiding this comment.
All conditions now log to FH
|
|
Close PR to facilitate conflict resolution. New PR #502 |



Summary
https://nhsd-jira.digital.nhs.uk/browse/VED-292
Changes:
Reviews Required
Review Checklist
ℹ️ This section is to be filled in by the reviewer.