Nomad: Syslog based log forwarding in Nomad client
Nomad should forward stdout and stderr log messages to an operator specified syslog endpoint. The syslog endpoint has to be specified in the Nomad client configuration file.
diptanu
All 5 comments
If possible, this should support adding the container name as a syslog tag. Otherwise it will be difficult to figure out which container the logs are coming from.
avinson
on 13 Aug 2016
+1
bsphere
on 14 Mar 2017
+1
dansteen
on 19 Jun 2017
We still need this guys +1
billykwooten
on 23 Aug 2017
https://github.com/adragoset/nomad_follower
Maybe a temporary solution for log forwarding until this is implemented. When run as a system task on every worker it will tail all allocations on the worker and write them to a single file with some metadata about the task specifically the allocation id and any service names defined in the service stanza of the task. If run in a task group with a log shipper of the operators choice the aggregate file can be shared and subsequently watched by the log shipper through the shared alloc folder. This allows nomad to still manage the logs for allocation tasks and prevents the operator from needing to run a log shipper in every task group.
adragoset
on 27 Apr 2018
Related issues
jrasell
路
3Comments
bdclark
路
3Comments
funkytaco
路
3Comments
Gerrrr
路
3Comments
jippi
路
3Comments
Most helpful comment
If possible, this should support adding the container name as a syslog tag. Otherwise it will be difficult to figure out which container the logs are coming from.