Log drains overview
Coolify log drains forward workload container output to an external logging destination. Configure one destination on a server, then enable log draining for the resources you want to include.
What log drains forward
Coolify starts coolify-log-drain on the server. Opted-in resource containers send their stdout and stderr to this local Fluent Bit container, which forwards the records to your destination.
Choose a destination
A server can have only one Coolify-managed log drain enabled at a time. Follow the destination guide for its credentials and configuration.
Configure the server
- Open Servers and select the validated server that runs the resources.
- Open Log Drains.
- Enter and save the settings for one destination while Status is Disabled.
- Set Status to Enabled to start
coolify-log-drain.
Enable log draining for a resource
The server drain must be enabled first. Otherwise, Coolify turns the resource's Log drain setting off again.
Open the application
Open the application, then select Advanced. This also applies to Docker Compose applications.
Enable Drain Logs
Under Logs, set Log drain to Send logs to the log drain endpoint.
Apply the change
Restart or redeploy the application.
Verify delivery
- Make the resource write a recognizable message to
stdoutorstderr. - Open the logging provider and search recent events for that message.
- If the event is missing, inspect the log-drain container on the resource server:
docker ps --filter name=coolify-log-drain
docker logs --tail 100 coolify-log-drainThe built-in Axiom and New Relic destinations flush every five seconds. A custom configuration uses its own Flush value.
Limitations
- A server can use only one Coolify-managed log drain at a time.
- Retention, queries, dashboards, and log-based alerts are managed by the external provider.
- Disabling the server drain stops forwarding but does not clear the saved Log drain settings on resources.