# GELF

Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fintegrations%2Fdocker%2Fgelf.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fintegrations%2Fdocker%2Fgelf.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

Action required by August 20, 2026: GELF ingestion endpoint deprecation

Coralogix will permanently disable native GELF ingestion on **August 20, 2026**. Migrate to a Logstash-based forwarder before the cutoff to avoid data loss. See the [GELF and UDP rsyslog deprecation notice](https://docs-docusaurus.kinsta.page/user-guides/latest-updates/deprecations/gelf-udp-rsyslog/.md) for full migration steps.

Coralogix provides a simple and seamless *Gelf integration driver for your* Docker logs. Ship your logs directly from your containers without having to install any SDK or agent, and get started in minutes. 

## [](https://github.com/coralogix/docker-gelf-example/blob/master/README.rst#usage)Usage[​](#usage "Direct link to usage")

This document includes cluster dependent URLs. Each URL has a variable part (in Italic). Please match this part with a row entry within the following table. Copy the table row entry located under the column that matches the top level domain of your Coralogix account (.com, .in etc.). Replace the variable part of the URL with this entry.

Provide the following four variables:

* **PRIVATE\_KEY** - Your [Send-Your-Data API key](https://docs-docusaurus.kinsta.page/user-guides/account-management/api-keys/send-your-data-api-key/.md) is a unique ID that represents your company.

* **COMPANY\_ID** - A unique number which represents your company. You can get your company id from the settings tab in the Coralogix dashboard.

* **APP\_NAME** - The name of your environment, for example, a company named *"SuperData"* would probably insert the *"SuperData"* string parameter or if they want to debug their test environment they might insert the *"SuperData–Test"*.

* **SUB\_NAME** - Your application probably has multiple components, for example, Backend servers, Middleware, Frontend servers etc. in order to help you examine the data you need, inserting the subsystem parameter is vital.

## [](https://github.com/coralogix/docker-gelf-example/blob/master/README.rst#example)Example[​](#example "Direct link to example")

If you run your containers manually:

```
docker run -dit \

 -e PRIVATE_KEY="XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" \

 -e COMPANY_ID=XXXX \

 -e APP_NAME="simple-application" \

 -e SUB_NAME="backend" \

 --log-driver=gelf \

 --log-opt gelf-address=udp://syslogserver.Cluster URL:20001 \

 --log-opt env=PRIVATE_KEY,APP_NAME,SUB_NAME,COMPANY_ID \

 alpine echo "Hello world!"
```

You can also use it with **docker-compose.yml**:

```
version: "3"

services:

  web:

    restart: always

    build: app

    container_name: flask-app

    # Setup required parameters for Coralogix integration

    environment:

      - PRIVATE_KEY=${PRIVATE_KEY}

      - APP_NAME=${APP_NAME:-flask-app}

      - SUB_NAME=${SUB_NAME:-backend}

      - COMPANY_ID=${COMPANY_ID}

    # Setup logging driver

    logging:

      driver: gelf

      options:

        # Address of Coralogix syslog server

        gelf-address: "udp://syslogserver.coralogix.com:20001"

        # Required parameters for request

        env: "PRIVATE_KEY,APP_NAME,SUB_NAME,COMPANY_ID"

    ports:

      - "5000:5000"
```

Before using this integration, make sure you create a **.env** file with configurations or write them directly to the **docker-compose.yml** file.

Now you should have your docker logs streaming to Coralogix. Not seeing your logs in our [LiveTail](https://docs-docusaurus.kinsta.page/user-guides/data_exploration/logs/livetail/.md)? Use our in-app chat for support. 

You can try to deploy our example application: [Source code](https://github.com/coralogix/docker-gelf-example).