By rbrazier
I’m trying to ship my webserver logs (done the application logs already) to a centralised log service, namely LogDNA.
They have a debian agent which I attempted to install using the PHP heroku builder, however I’m getting ‘No route to host’ when trying to download the agent GPG key from https://repo.logdna.com (see https://docs.logdna.com/docs/ingestion-methods), do you have an allowlist of domains during the build stage?
Currently I’m installing the agent during the build commands and then starting it in the run commands.
Additionally, the package installation requires using apt-get, which isn’t accessible with the build user, is there any way to add a package and source to the initial “Installing platform packages…” stage.
Would I be able to configure this using the Heroku builder with some additional configuration or would this need to be using a custom Dockerfile? I feel like the ‘No route to host’ issue would still be there though
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Heya,
Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.
App Platform currently doesn’t support installing additional software via apt-get or including additional third-party repositories during the build phase. It means you won’t be able to install the LogDNA agent this way. Also, the accessibility to external URLs during the build phase is limited, thus you might face the 'No route to host error.
The general recommendation is logging to stdout or stderr, the DigitalOcean App Platform then collects and aggregates these logs for you. If you want to use a centralized log service like LogDNA, an alternative to installing the agent would be to use the LogDNA API and have your application manually send logs to them.
You may also consider using a custom Dockerfile, but again, connecting to external URLs during the build phase might lead to similar issues.
Check the DigitalOcean docs particularly the App Platform section for further help:https://www.digitalocean.com/docs/app-platform/.
Hope that this helps!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.