Currently the only logging my application does is through console logging directly in the main process output of my application. It's somewhat difficult to get a sense of what is happening in production due to the fact that fly.io only keeps the last 100 lines or so of that output available with it's own logging functionality. It would be great to be able to see the history from much further back. I also just don't really log what is happening in the application and so have little visibility into what is actually happening from a business logic standpoint. Ideally to close this ticket, the following things should be implemented:
[ ] Add a formal logging implementation to my application. Ideally the Play framework has something available to me which I can use. If not, I should find a Scala library which does this. And if nothing else, I could implement my own. I'm thinking the implementation will log to different files under the logs directory in my application. I will have to see how that would work in production as I believe I'm going to have to setup a mounted volume in fly.io to hold the logs.
[ ] Add logging throughout the application. I'm thinking of copying something similar to what we do in our API for work, where each log shows the class its logging from as well as the data I am trying to log and any contextual information that goes with it. I'll have a separate ticket for researching and documenting the logging scheme and implementation.
[ ] Create a persistent volume in Fly.io to hold the logs. I'm not exactly sure how much space I can use in the current VM instance and fly.io seems to have an official way to dedicate disk space for the app. I'll probably set it to 1GB for now. I will have to set up a purging mechanism for the logs so I can keep them well within the size of the diskspace.
Currently the only logging my application does is through console logging directly in the main process output of my application. It's somewhat difficult to get a sense of what is happening in production due to the fact that fly.io only keeps the last 100 lines or so of that output available with it's own logging functionality. It would be great to be able to see the history from much further back. I also just don't really log what is happening in the application and so have little visibility into what is actually happening from a business logic standpoint. Ideally to close this ticket, the following things should be implemented: