Skip to content
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

agent syslog always runs at NOTICE level #15087

Closed
tgross opened this issue Oct 31, 2022 · 4 comments
Closed

agent syslog always runs at NOTICE level #15087

tgross opened this issue Oct 31, 2022 · 4 comments
Labels
Milestone

Comments

@tgross
Copy link
Member

tgross commented Oct 31, 2022

The rarely-used enable_syslog configuration emits Nomad agent logs to a syslog interface. While debugging a problem for an internal user, I noticed that they were only getting high-level logs. When we configure syslog at command.go#L478 we set the log-level to NOTICE, which means even if the agent is set to log at debug, only NOTICE-level and below will actually get emitted on the syslog interface.

(Note this is entirely unrelated to any allocation logs, which are covered under other open issues.)

@tgross tgross added the help-wanted We encourage community PRs for these issues! label Oct 31, 2022
@sharmaansh21
Copy link

sharmaansh21 commented Nov 14, 2022

Hi @tgross Can I pick this issue?

@jrasell
Copy link
Member

jrasell commented Nov 14, 2022

Hi @sharmaansh21; we do not have a formal way to assign this issue to you, but we are not currently working on it internally, so please feel free to pick this issue up. If you have any questions, please do not hesitate to reach out to us via this issue. Thanks for showing interest!

@tgross
Copy link
Member Author

tgross commented Jan 4, 2023

Fixed by #15625 and will ship in the next regular release of Nomad.

@tgross tgross closed this as completed Jan 4, 2023
@tgross tgross added this to the 1.4.4 milestone Jan 4, 2023
@github-actions
Copy link

github-actions bot commented May 5, 2023

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Development

No branches or pull requests

3 participants