text: Title: [Question] How to get logs like Zappa
  Body: Hi there
  
  I followed this tutorial to get FastAPI up into a Lambda function: https://adem.sh/blog/tutorial-fastapi-aws-lambda-serverless
  
  It seems to be working, but when I tail the logs (`sls logs --function app --stage test`), I see my 'hello' INFO log in there, but it's enclosed in a large block of other logging. It looks like the following:
  
  ```
  START
  2022-02-13 13:58:36,501 Event received.
  2022-02-13 13:58:36,501 Waiting for application startup.
  2022-02-13 13:58:36,501 LifespanCycleState.STARTUP:  'lifespan.startup.complete' event received from application.
  2022-02-13 13:58:36,501 Application startup complete.
  2022-02-13 13:58:36,501 HTTP cycle starting.
  2022-02-13 13:58:36,502 hello
  2022-02-13 13:58:36,502 HTTPCycleState.REQUEST:  'http.response.start' event received from application.
  2022-02-13 13:58:36,502 HTTPCycleState.RESPONSE:  'http.response.body' event received from application.
  2022-02-13 13:58:36,503 Waiting for application shutdown.
  2022-02-13 13:58:36,503 LifespanCycleState.SHUTDOWN:  'lifespan.shutdown.complete' event received from application.
  END Duration: 3.55 ms	Billed Duration: 4 ms	Memory Size: 1024 MB	Max Memory Used: 79 MB
  ```
  
  What would I need to do to tail nice coloured logs like I'm used to with Flask/Zappa with the option to filter them? Ideally calls to each endpoint would be logged on a single line, my own log statements would be a single lines, and the uncaught exceptions would also be visible. Basically, I'd like to tail the cloud logs so that they look as similar to the local FastAPI logs as possible.