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

log_level config for munin itself #1530

Open
cweiske opened this issue Apr 16, 2023 · 0 comments
Open

log_level config for munin itself #1530

cweiske opened this issue Apr 16, 2023 · 0 comments

Comments

@cweiske
Copy link
Contributor

cweiske commented Apr 16, 2023

Is your feature request related to a problem? Please describe.
I'm using CGI for graphing and HTML generation.
Nevertheless both munin-graph.log and munin-html.log get a new line every 5 minutes telling me that

2023/04/16 11:00:06 [INFO] graphing is cgi, do nothing
2023/04/16 11:05:07 [INFO] graphing is cgi, do nothing
2023/04/16 11:10:07 [INFO] graphing is cgi, do nothing

and

2023/04/16 11:00:06 [INFO] config generated (0.02 sec)
2023/04/16 11:00:06 [INFO] html_strategy is cgi. Skipping template generation
2023/04/16 11:05:07 [INFO] config generated (0.02 sec)
2023/04/16 11:05:07 [INFO] html_strategy is cgi. Skipping template generation
2023/04/16 11:10:07 [INFO] config generated (0.02 sec)
2023/04/16 11:10:07 [INFO] html_strategy is cgi. Skipping template generation

I know that. I don't want the logs filled with that info.

Describe the solution you'd like
A log_level config option for munin that behaves similar to log_level for munin-node.

Describe alternatives you've considered
I could hack my log level into /usr/share/munin/munin-graph as described in https://stackoverflow.com/questions/10646309/how-to-change-log-level-of-munins-munin-graph-log-munin-html-log-munin-limits
but that would mean I lose the change with the next update.

Additional context
Debian 11, munin 2.0.67-3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant