Better logging of exceptions in authenticator
As an engineer I want logs to stay in the json format for easier searchability
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @jjshoe -
Service:: or C:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
Adjust formatting and/or error handling to log as JSON
-
-
Acceptance testing passed -
Deployed to production
Notes
It looks as if it starts to log it ok, but then falls apart when the stack trace gets dumped. The following link in the production aws account should help you find samples: https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logsV2:logs-insights$3FqueryDetail$3D$257E$2528end$257E0$257Estart$257E-172800$257EtimeType$257E$2527RELATIVE$257Eunit$257E$2527seconds$257EeditorString$257E$2527fields2040timestamp2c2040message0a7c20filter2040timestamp20like202f163232830622f0a7c20sort2040timestamp20desc0a7c20limit2020$257EisLiveTail$257Efalse$257EqueryId$257E$2527de0b984b-e616-4a9a-a313-591a2c25eaaf$257Esource$257E$2528$257E$25272faws2fecs2fauthenticator2fproduction*2f$2529$2529