I currently use loggly-python-handler to log an application that has asynchronous jobs triggered by web requests. To do this, I use os.fork to fork off the actual job, and use the original request to respond back to the web request as ok. No matter what I do, I only receive logs in loggly for the original process, and nothing for the forked process. This is true when trying to use my global logger, or even instantiating a new object via logging.getLogger() after the fork. Is there something under the hood that stops me from using the original logger no matter where the object is referenced?
I currently use loggly-python-handler to log an application that has asynchronous jobs triggered by web requests. To do this, I use os.fork to fork off the actual job, and use the original request to respond back to the web request as ok. No matter what I do, I only receive logs in loggly for the original process, and nothing for the forked process. This is true when trying to use my global logger, or even instantiating a new object via logging.getLogger() after the fork. Is there something under the hood that stops me from using the original logger no matter where the object is referenced?