-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use tcp in --gelf-address #29871
Comments
I think GELF only supports UDP; see http://docs.graylog.org/en/2.1/pages/gelf.html (and the library that's used ping @mariussturm |
Yes right, currently only UDP is supported. |
Thanks @mariussturm @rajasekaran07 given the discussion above, I'm closing this issue, because it cannot be implemented in docker currently. Feel free to ping me though if it's implemented in GELF at some point. Also note that we are working on an option to have external logging driver plugins (see #28403), which would more easily allow to add custom logging drivers to docker that have features that are not part of the "core" docker functionality |
@thaJeztah @mariussturm Can we add additional tags in awslogs driver. Because while taking logs using awslogs driver we are getting minimal information. (Only container ID), How can I take image name, container name and host IP. Regards, |
@rajasekaran07 what is the awslogs driver? Anyway this is a support question that should go the IRC channel or mailing list. GH issues are used for bug reports in Docker itself. Thanks. |
@rajasekaran07 more options coming to the awslogs driver in docker 1.13, see #27707, and docker/docs#380 |
@mariussturm awslogs driver is a docker log driver, which stream docker logs to AWS Cloudwatch log group. But it only taking container ID. I am trying to get all docker information like image name, host ip.. etc... |
FYI Gelf TCP is supported with the 17.12 ce as seen in the docs |
Hello,
We are running our application in AWS ECS and we are trying to collect our container logs via TCP port using gelf log driver. But if I used TCP in --log-driver-options --gelf-address tcp://ipaddress:port my container is not starting.
docker: Error response from daemon: gelf: endpoint needs to be UDP.
Kindly suggest how to use TCP in gelf-address option.
My docker version is 1.12
Regards,
Raja
The text was updated successfully, but these errors were encountered: