You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finding a decent solution for centralized, multi-tenant logging with Nomad is ... difficult ... at the moment, especially when the desire is to keep nomad logs working alongside a centralized log shipping solution.
Our current approach is to inject a Filebeat based sidecar per task that adds several additional fields that are absolutely necessary in multi-tenant setups :
... but with several hundred sidecars running this is not really feasible any longer :(
But if the names of the actual log files generated by Nomad could be changed to include more than just the task name the above problem could be solved by running a single log shipper per host.
Inspired by the metrics format that Nomad uses an example could be :
<Namespace>.<Job>.<TaskGroup>.<Task>.stdout.0
Based on the path and filename we could then route the correct logs to the correct teams and enable much easier correlation between the logs and metrics that Nomad offers.
The text was updated successfully, but these errors were encountered:
Finding a decent solution for centralized, multi-tenant logging with Nomad is ... difficult ... at the moment, especially when the desire is to keep
nomad logs
working alongside a centralized log shipping solution.Our current approach is to inject a Filebeat based sidecar per task that adds several additional fields that are absolutely necessary in multi-tenant setups :
... but with several hundred sidecars running this is not really feasible any longer :(
But if the names of the actual log files generated by Nomad could be changed to include more than just the task name the above problem could be solved by running a single log shipper per host.
Inspired by the metrics format that Nomad uses an example could be :
<Namespace>.<Job>.<TaskGroup>.<Task>.stdout.0
Based on the path and filename we could then route the correct logs to the correct teams and enable much easier correlation between the logs and metrics that Nomad offers.
The text was updated successfully, but these errors were encountered: