-
-
Notifications
You must be signed in to change notification settings - Fork 28
Configure logging #92
Comments
Currently none of the projects have a persistence for logs, sure we do have some tools like opbeat and datadog but, we would want to have our own solution preferably cheap (as in free) like https://www.elastic.co/solutions/metrics We are exploring options for hosting them on our own. |
Thanks! Is Datadog giving us a good deal, the lack of data retention over 24 hours in the free tier sounds like a blocker. As Opbeat has been acquired by Elastic thats a dead end. The Elastic offerings sound interesting. I have seen quite a high operational load on keeping an ELK stack performing at scale, which makes me a little wary of using it in a small team. However How far are you in exploring running a self hosted ELK? Shall we set up a call this week and catch up? |
I am planning to re-route the beta instance logs to a small EC2 instance on AWS as a spike with the elastic stack. I am unsure when I will get that ready though. It will need some changes on the beta itself. But yeah I am up for a call around Thursday if you would like to catch up. Will send you an invite. |
We've had our meeting and decided to use Cloudwatch for now. What remains to do for this issue is to improve log messages by adding the API GW ID Lambda see https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-logging.html |
Where do our logs go, what do other freeCodeCamp project do? Can and if so, are we happy to re-use this?
/cc @freeCodeCamp/open-api
The text was updated successfully, but these errors were encountered: