Lost logs from threads

[Geary-Layne]

Linear Issue

IDSSE-1011

Changes

• There wasn't so much as a bug, as missing logic
  • We use python's ContextVars to make corr_id available to logging
  • It turns out that a thread doesn't inherit ContextVars automatically
  • There are two ways to get logs from threads
    • 1. We can initialize our logger to not use corr_id logging.config.dictConfig(get_default_log_config('INFO', with_corr_id=False))
    • 2. Pass ContextVars to threads
  • I added tests two test_log_util.py that test getting logs from a thread running a function and from Classes that extend Threads
  • I added passing ContextVars to Consume/Publisher in rabbitmq_utils.py
• There are likely other places in our code that logs are getting lost in threads, and the test in log_util.py will serve as example code

Explanation

N/A

[mackenzie-grimes-noaa]

I had never heard of Python ContextVars before. From the docs it looks like it's effectively a dictionary where you can hide variables to sneak them across the scope borders of individual threads. Not sure how Python does it, but if it works it works.