OpenTechFund / bypass-otf_proxy

1 stars 1 forks source link

Log reporting - Meta issue #25

Closed maxpearl closed 3 years ago

maxpearl commented 3 years ago

This is a meta-issue for all log reporting. Ultimately, we want to provide information about use of the alternatives. We have:

Logs are created and need a storage process somewhere. Right now, we have a local log directory, as well as an s3 bucket for log storage. Azure is going to require it's own storage.

maxpearl commented 3 years ago

Before I tackle this, I want to do #9, so that we can get different logs for different domains from different s3 buckets, allowing for a more distributed system.

maxpearl commented 3 years ago

Cloudfront is now done. https://github.com/OpenTechFund/bypass-otf_proxy/commit/31d56d5cbe0d6894785b12faa299aafac98c1a69

maxpearl commented 3 years ago

Fastly docs on log streaming are pretty straightforward. The challenge is that the logs and file names will not distinguish between the 5 endpoints served in that service. So it is probably going to involve some processing to figure that out. Also, will need to figure out how to connect the cloudfront logs for the same endpoint.

maxpearl commented 3 years ago

Azure, Fastly, Cloudfront and Nginx logs set up and seem to be working. Might need tweaks in the future, but closing this, as the work has been completed.