Better logging and error handling for pollers

[bryophyta]

What does this change?

Add structured logging to poller lambdas:

• Change loggingFormat to 'text' instead of JSON, for compatibility with our lambda log shipping stack.
• Add logger abstraction inspired by: https://github.com/guardian/service-catalogue/pull/1131/files
  • Extended by allowing us to set 'default' fields in the logging, akin logmarkers.
  • Adjust the poller function definition to allow passing in a logger from the poller wrapper
• Add invocation and error logging to poller lambda wrapper, and error logging to the Reuters poller

By adding metadata like sqsMessageId to logging, it should be easier to track issues in the logs. Currently plain console.log etc. are still used in the body of the poller functions, but if we like this pattern then we could convert these, and possibly add an eslint rule to enforce using logger. rather than console..

How to test

• Deploy to CODE, check that logs come in as expected

How can we measure success?

Have we considered potential risks?

Images

Accessibility

• Tested with screen reader
• Navigable with keyboard
• Colour contrast passed
• The change doesn't use only colour to convey meaning

[github-actions]

Deploy build 681 of Editorial Tools::News Wires to CODE

All deployment options

• Deploy build 681 of Editorial Tools::News Wires to CODE
• Deploy parts of build 681 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.