-
Notifications
You must be signed in to change notification settings - Fork 2k
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
“tail -f” logs for a job for all instances #10308
Comments
Hi @tolitius, this is a great suggestion. Smaller quality of life improvements like this tend to be overlooked when we're planning out work for the Nomad roadmap. If this is something folks would really find useful, please definitely leave a 👍 |
👉 in case anyone has a need to tail / grep logs from all allocations for a job in one place
|
a livesaver! It would be nice if it had colours |
@tolitius I raised a PR to your repo. |
@maxadamo merged, thank you! |
Proposal
there is kubetail which enables you to aggregate (tail/follow) logs from multiple pods into one stream. This is the same as running "
kubectl logs -f
" but for multiple pods. … but it is for kubernetes.tails logs of a single, random instance of a job which is only “somewhat” useful.
yes, logs from multiple instances can be/are shipped to ELK/splunk, etc…
but they are available on all nomad instances, and while some ssh mockery with a poor user experience can be done, it is just that: not great.
we can do better.
nomad knows about the mounts OR about the logs that are available in stdout.
the proposal is to enable
nomad logs
to tail logs from all instances for a given app: similar to kubetail.something like this:
to see the logs in the terminal from all instances of a job.
this conversation has started on hashicorp discuss where @jrasell recommended to create an issue
Use-cases
any time logs need to be inspected (i.e. most of the time) logs from all instances for an app are needed.
a log from a single, random instance is rarely useful.
Attempted Solutions
I currently do somm like this, but it is a bit limited since it does not differentiate logs per host, does not colorize it, etc..
The text was updated successfully, but these errors were encountered: