feat: query and answer logging#200
Conversation
Terraform Format and Style 🖌
|
aliziel
left a comment
There was a problem hiding this comment.
I'll double check the ECS logs after deploy to make sure the AWS drivers are compatible with the Uvicorn/Fast setup.
Not a blocker, but would it be easy and safe to also include the streamed response messages that are accessible to the client ? I realize size may be a concern, but those XResponseMessages that get printed in devtools could be valuable information to retain serverside with the current query/answer change
Yeah, I chose to just to the query and the answer to avoid spamming the logs. We could add it, but I think i'd be worried about creating too much noise. |
Closes #108. Includes a custom logging config for uvicorn (thanks Claude!) and hooks it into
docker-compose.yamland Terraform.Testing locally, we got log messages like this:
This should show up in CloudWatch no problem, and you can do a filter on
atlas_assistant.apito get log messages from the API.My editor did some auto-formatting of the Dockerfile, apologies.
Checklist
uv run prek run --all-files)uv run pytest --integration)