Coolify logoCoolify
Cloud

Send logs to Axiom

Coolify's built-in Axiom log drain sends opted-in resource logs to an existing Axiom dataset over HTTPS.

The short version

Create an Axiom dataset and ingest-capable API token, save both values on the server's Log Drains page, enable the Axiom drain, then enable Drain Logs and restart each resource you want to forward.

Before you start

Axiom datasetCreate the dataset that will receive the forwarded workload records.
API tokenCreate a token that can ingest events into the selected dataset.
Validated serverUse the server that runs the resources and confirm it can reach api.axiom.co on port 443.

Create the dataset and token in Axiom, then copy their exact values before opening Coolify. Coolify accepts letters, numbers, underscores, hyphens, and periods in both Axiom fields.

The built-in integration sends data to api.axiom.co on port 443. This endpoint is not configurable from the Axiom section in Coolify.

Configure Axiom in Coolify

Connect the server to Axiom

Keep the drain disabled while editing its fields, then enable it after the values are saved.

1

Open the server Log Drains page

2

Enter the API key

3

Enter the dataset name

4

Save the Axiom settings

5

Enable the drain

  • Open Servers, select the server that runs the resources, then open Configuration > Log Drains.
  • In Axiom, leave Enabled off and paste the Axiom token into API Key.
  • Enter the exact dataset name in Dataset Name.
  • Select Save in the Axiom section.
  • Turn on Enabled. Coolify starts the server's coolify-log-drain container.

Only one server-level log drain can be enabled at a time. Disable another active destination before enabling Axiom.

Enabling the drain is not an ingestion test

Coolify checks that both fields are present and use accepted characters. It does not verify the token, dataset permissions, or Axiom ingestion before showing the drain as enabled.

Enable a resource

Follow Enable log draining for a resource, then restart or redeploy the resource.

The Axiom configuration sends logs as gzip-compressed JSON, writes the event time to _time in ISO 8601 format, and flushes every five seconds.

Identify logs

The built-in configuration adds fields that help you filter records.

Built-in log identification

The server label is automatic. The resource label is added only when the resource provides COOLIFY_APP_NAME.

Server label

coolify.server_name
  • Added automatically to every record
  • Identifies the Coolify server that forwarded the record

Resource label

coolify.app_name
  • Created from the resource environment variable COOLIFY_APP_NAME
  • Available after you save the variable and restart the resource

For example, add this environment variable to the resource:

COOLIFY_APP_NAME=web

The built-in filter excludes log records whose message contains 127.0.0.1. Local health-check requests may therefore be absent from the dataset.

Verify delivery

  1. Cause the resource to write a recognizable message to stdout or stderr.
  2. Wait at least five seconds.
  3. Open the Axiom dataset and search recent events for the message, coolify.server_name, or coolify.app_name.

Verification in Axiom is required because Coolify does not perform a provider connection test.

Update the dataset or token

  1. Turn off Enabled in the Axiom section.
  2. Update API Key or Dataset Name.
  3. Select Save.
  4. Turn on Enabled again.
  5. Generate a new resource log and confirm that it arrives in the expected dataset.

Fix missing logs

  1. Confirm Axiom is the enabled server drain and the resource's Drain Logs setting is on.
  2. Confirm you restarted or redeployed the resource after enabling the setting.
  3. Confirm the token can ingest into the exact dataset name entered in Coolify.
  4. Confirm the server can reach api.axiom.co:443.
  5. Inspect the Fluent Bit container on the resource server:
docker ps --filter name=coolify-log-drain
docker logs --tail 100 coolify-log-drain

Authentication, dataset, and network errors appear in the Fluent Bit output.

Continue with log drains

Log drains overview

Review the server-level pipeline, resource setup, and delivery checks.

Use New Relic

Send opted-in workload logs to the regional New Relic Log API.

Use custom Fluent Bit

Supply a complete Fluent Bit configuration for another destination.

Overview

Understand how Coolify forwards application, database, and service container logs to an external destination.

New Relic

Send Coolify application, database, and service container logs to New Relic Logs.

On this page

Send logs to Axiom
Before you start
Configure Axiom in Coolify
Enable a resource
Identify logs
Verify delivery
Update the dataset or token
Fix missing logs
Continue with log drains