mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 17:35:54 +03:00
[GH-ISSUE #160] Log Level not filtering some data #65
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#65
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ricardoper on GitHub (Sep 18, 2019).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/160
Hello,
When I startup this app I see a lot of verbose logs that I not want based on my configuration file:
Output:
Can you check this?
Best regards,
Ricardo Pereira.
@mageddo commented on GitHub (Sep 18, 2019):
I'll make some checks, did you notice this regression from some version?
Please check if haven't set MG_LOG_LEVEL env variable cause it has precedence
@ricardoper commented on GitHub (Sep 18, 2019):
Hello @mageddo,
I don't have that env variable defined.
I always see this logs since I used it (about 4 months), but now I report it because I need cleaner logs.
Best regards,
Ricardo Pereira.
@mageddo commented on GitHub (Sep 19, 2019):
I see, the question is the log level is changed after some steps, then you will see some logs before the log is changed
@mageddo commented on GitHub (Sep 19, 2019):
2.18.1 was released fixing the issue, can you check it?
@ricardoper commented on GitHub (Sep 19, 2019):
Hello @mageddo,
Almost perfect. There is a WARNING line that escapes the filter:
Thanks for the fast release,
Ricardo Pereira
@mageddo commented on GitHub (Mar 4, 2023):
unfortunately some logs will output before the program reach the point to change the log level, I think in this you can forward the logs to /dev/null or
grep ERRORto filter only errors.I will close the issue considering it partially fixed as won't be able to fix it completely