Runtime Logs storage location/limit.

Heya @renanbarbosasilva,

Runtime logs storage:

DigitalOcean App Platform stores logs for each of your app’s components, including services, workers, and jobs. While the logs are not stored in a specific directory within your app, you can access them through the DigitalOcean Control Panel or using the DigitalOcean CLI (doctl).

To view logs in the Control Panel, navigate to your app’s page, then click on the specific component (e.g., service, worker, etc.) for which you’d like to see logs. You’ll find a “Logs” tab that shows the most recent logs for that component.

To access logs using the DigitalOcean CLI, first, make sure you have doctl installed and authenticated. Then, you can run the following command, replacing <app-id> with your app’s ID and <component-name> with the name of the component for which you’d like to view logs:

doctl apps logs <app-id> --component=<component-name>

Runtime logs and RAM memory consumption:

Logs generated by your application should not be kept in your app’s RAM memory by default. The increased RAM consumption you are observing might be due to other factors such as a memory leak or increased workload in your app.

However, if you’ve configured your application to store logs in memory (e.g., using an in-memory datastore like Redis), this could contribute to increased RAM consumption. In this case, you should consider storing logs in an external service or periodically flushing the in-memory datastore to manage memory usage better.

Hope that helps!