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.
Provide the following four variables:
- PRIVATE_KEY – A unique ID which represents your company, this Id will be sent to your mail once you register to Coralogix.
- 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.
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.coralogix.com: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:
# Setup required parameters for Coralogix integration
# Setup logging driver
# Address of Coralogix syslog server
# Required parameters for request
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 Coalogix. Not seeing your logs in our LiveTail? Use our in-app chat for support.
You can try to deploy our example application: Source code.
Signup to Coralogix