-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Allow for logfile naming like in Nomad #15709
Comments
CC @wjpatton |
Linking to a related issue: #10976 |
It seems to me that without that feature, one cannot properly integrate datadog log collection. The link on their docs shows that the datadog agent configuration requires specifying a file path: https://docs.datadoghq.com/integrations/consul/?tab=host#log-collection With the current naming scheme, I fail to see how we can always point to an up to date source of logs |
@Esity Just to clarify, |
Recent/new logs would go to consul.log Let me know if that makes sense |
Feature Description
Currently consul logs files like this
consul-{timestamp}.log
This is a pain to figure out the most recent log file. Sure we collect files and ship them out but sometimes it's useful to look inside /var/log
Nomad Example
But consul looks like this
Nomad Config Code
https://github.com/hashicorp/nomad/blob/1c9b4e398dd2b954dc0414b7c1568f04a3143355/command/agent/config.go#L66
https://github.com/hashicorp/nomad/blob/1c9b4e398dd2b954dc0414b7c1568f04a3143355/command/agent/config.go#L1326-L1328
Consul Config Code
consul/agent/config/config.go
Line 193 in 36f05bc
Use Case(s)
The use here is to make this easier to tail the most recent log file
The text was updated successfully, but these errors were encountered: