Open rajasekaran07 opened 7 years ago
Hi @rajasekaran07 - I am facing the same issue in my setup. Has this issue been addressed or do you have any updates on this maybe from other threads?
If it is not yet supported to use gelf driver over TCP then I will look into using alternative drivers such as fluentd.
Thank you, Daniel
Yes...
I used fluentd. Gelf is not supported to TCP.
Regards, Raja 9042070117
On 09-May-2017 12:47 am, "Daniel" notifications@github.com wrote:
Hi @rajasekaran07 https://github.com/rajasekaran07 - I am facing the same issue in my setup. Has this issue been addressed or do you have any updates on this maybe from other threads?
If it is not yet supported to use gelf driver over TCP then I will look into using alternative drivers such as fluentd.
Thank you, Daniel
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/awslabs/ecs-cloudwatch-logs/issues/9#issuecomment-299963582, or mute the thread https://github.com/notifications/unsubscribe-auth/ASTgiCxKvwvlbSBsWbWW4_eySIzBVnugks5r32o-gaJpZM4LaTxT .
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