Related

Why am I getting a Deploy Error: Health Checks? Question Question
How can I see the build logs for my application if the build was skipped for a deployment? Question Question

Question

How can App Platform container logs be retained?

Posted October 12, 2020 388 views
DigitalOcean App Platform

How can the container logs sent to /dev/stdout and displayed in Logs section of App Platform be simultaneously transported to a remote logging facility like Papertrail or any other remote logging servers?

Add a comment
By:
ghimire

Related

Why am I getting a Deploy Error: Health Checks? Question Question
How can I see the build logs for my application if the build was skipped for a deployment? Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers
snormoredo October 12, 2020

@ghimire 👋

We don’t currently have a direct integration with streaming logs to external services built into the platform, but this is something we are considering for the future, so stay tuned. Your feedback on this is definitely appreciated. In the meantime, you would need to instrument your application code directly to produce logs to the external service.

Reply Report
michiel October 22, 2020

Certain log services (such as Papertrail) also have a “native” component for your web framework. For example, you can log straight from your Rails app into Papertrail via the remote_syslog_logger gem. Check out the second piece of this article on that: https://documentation.solarwinds.com/en/Success_Center/papertrail/Content/kb/configuration/configuring-centralized-logging-from-ruby-on-rails-apps.htm?cshid=pt-configuration-configuring-centralized-logging-from-ruby-on-rails-apps

Maybe your framework also offers a way to log directly into Papertrail.

Reply Report
  • ghimire October 23, 2020

    Thank you for your response.

    Since we have multiple programs logging in to /dev/stdout and /dev/stderr, we opted to use supervisord whose stdin and stdout can be logged in to a file. We then transported those log files to remote syslog server via https://github.com/papertrail/remote_syslog2 in run_command before launching Docker Entrypoint. This has helped us remain web framework and server agnostic.

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help