Drain Logs
You can drain logs of your deployed services to a third-party applications like Axiom or New Relic.
We will support more services in the future, like Signoz, HyperDX, etc.
How to enable?
-
Enable on your Server.
- First, you need to enable it on your
Serversettings. - Go to your
Serverwhere you want to enable theDrain Logsand click on theLog Drainstab.
- First, you need to enable it on your
-
Enable on your Resource.
- Go to your resource,
Advancedtab and enable theDrain Logsfor the resource.
- Go to your resource,
Caution
Once you enabled at least one of the Drain Logs, you need to Restart your
service to apply the changes.
How to configure?
Axiom
You need to have a Dataset and an API key from Axiom.
More information here.
New Relic
You need to have an License key from New Relic.
More information here.
Identify logs by application (per-service names)
If you run multiple services (e.g. web, worker, db) and want to split logs by service in New Relic, add a stable app name to every log event.
How to enable
-
Go to your resource -> Configuration -> Environment Variables and add
COOLIFY_APP_NAME=web(use any short identifier like web, worker, db, etc.).  -
Restart the resource for the change to take effect. (Log drains & env changes apply on restart.)
When COOLIFY_APP_NAME is present, New Relic will receive a coolify.app_name attribute which you can use to filter logs by service in New Relic.
Custom FluentBit configuration
If you know how to configure FluentBit, you can use the Custom FluentBit configuration to configure the drain logs.
Persistent Storage
Configure persistent Docker volumes and bind mounts for Coolify resources to preserve data between deployments with proper path mapping and sharing options.
Rolling updates
Deploy zero-downtime application updates with Coolify rolling updates using health checks, default container naming, and graceful container transitions.
