Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIAD-2671: Output dead letter message at INFO level #817

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

adrianclay
Copy link
Collaborator

Why

In the event that an MHS inbound message cannot be processed it would be useful to be clear what happens to the message once the error happens.

By outputing this at DEBUG level this message wouldn't have been displayed in a production like environment, making it harder for the NME to know what's happened to the corrupt message.

Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users
  • A corresponding change has been made to the Mapping Documentation repository

In the event that an MHS inbound message cannot be processed it would
be useful to be clear what happens to the message once the error happens.

By outputing this at DEBUG level this message wouldn't have beeen
displayed in a production like environment, making it harder for the
NME to know what's happened to the corrupt message.
@adrianclay adrianclay enabled auto-merge (squash) September 12, 2024 10:48
@adrianclay adrianclay merged commit 003801b into main Sep 12, 2024
1 check passed
@adrianclay adrianclay deleted the NIAD-2671-improve-dead-letter-logging branch September 12, 2024 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants