Ability to override Nomad's generated log filename

[DamianArado]

Proposal

I was following this doc, and I found out that there is currently no option to override the filename of the logs generated by Nomad (<task-name>.<stdout/stderr>.<index>) with Nomad config.
However, it would be quite helpful if that's also supported using the job definition itself.
In that case, I would just mount alloc/logs somewhere on my vm and then ship log files from there without writing any custom log naming and rotation mechanisms.
So, the whole flow would become quite easier for us.

App emits logs -> files get rotated and saved on VM -> ship to any logs aggregator

Use-cases

For running custom log rotation and log shipping scripts on predictable log filenames.

Attempted Solutions

In Python, I overrode Nomad's in-built log rotation mechanism by using TimedRotatingFileHandler and building a custom log shipping script that runs as a CRON, but it will become cumbersome for me to repeat this for other languages as we run multiple custom dockerized apps on Nomad.

[pkazmierczak]

Hi @DamianArado, thanks for the suggestion. The reason we have a naming pattern for allocation logs is because there are API endpoints that rely on it. But I think it could be a good idea to make that customizable? I'll mark it up for discussion.