So, I’ve a logging setup for
docker driver (thanks to this post) and get logs with enriched metadata.
However, my questions are more for
raw_exec driver. I don’t seem to find enough docs/config options to get this up and running myself, hence asking here.
Currently, Nomad stores the stdout/stderr logs inside
alloc/logs/ directory. If the task is executing as
exec, there’s no way to access these logs from the host. The typical solution of running a log collection agent (like
vector) as a system job and read logs from a common directory (like
/var/logs) isn’t possible, because Nomad currently doesn’t provide the option to configure a logging directory.
So, is the only choice to run a log collection agent as a
sidecar task, which has access to
/alloc/logs directory and collect it from there?
EDIT: I can also run
vector as a
system job and collect logs from
/opt/nomad/data/allocs/ folder. But the biggest issue here is that I won’t know which particular
group the alloc belongs to, unless I query Nomad API somehow before collecting the logs.
This seems a bit too hard than it should be Just wondering if I am missing out on something