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.

Sign up for GitHub

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

Jump to bottom

Make nginx respect logger: default settings #6828

Closed
TheQue42 opened this issue Jun 17, 2023 · 8 comments
Closed

Make nginx respect logger: default settings #6828

TheQue42 opened this issue Jun 17, 2023 · 8 comments
Labels
enhancement New feature or request stale

Comments

@TheQue42
Copy link

Describe what you are trying to accomplish and why in non technical terms
Running 0.12.1-367d724, and I have configured logging as:

logger:
  default: warning
  logs:
    frigate.mqtt: warning

But the nginx is still continuously logging with:

2023-06-17 09:20:04.173117802  1.2.3.4 - - [17/Jun/2023:09:20:04 +0200] "GET /api/stats HTTP/1.1" 200 3594 "-" "HomeAssistant/2023.6.2 aiohttp/3.8.4 Python/3.11" "-"

Describe the solution you'd like
To be able to set NGINX logs to warning, to reduce log output.

Describe alternatives you've considered
Tried adding frigate.nginx: warning, but it seems to be ignored.

Additional context
@TheQue42 TheQue42 added the enhancement New feature or request label Jun 17, 2023
@NickM-27
Copy link
Sponsor Collaborator

Those logger fields are only applied to python, I'm not sure nginx supports dynamic logging like that.

@insound
Copy link

insound commented Jun 19, 2023 •
edited
Loading

IDK, but i guess there is no any help or debug from this logs, and mb should be better add access_log off; in nginx.conf inside docker contaier.

@LeoI5
Copy link

LeoI5 commented Jun 19, 2023

Same problem. Messages are dropping once a second or more

@NickM-27
Copy link
Sponsor Collaborator

NickM-27 commented Jun 19, 2023 •
edited
Loading

IDK, but i guess there is no any help or debug from this logs, and mb should be better add access_log off; in nginx.conf inside docker contaier.

There are plenty of times where these logs have already been helpful for us debugging issues.

@skrashevich skrashevich mentioned this issue Jun 19, 2023
Closed
@NickM-27 NickM-27 mentioned this issue Jul 10, 2023
Closed
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 20, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2023
@TheQue42
Copy link
Author

Trying to follow the linked tickets, but it seems this whole issue has become stale? :-(

@pissten
Copy link

pissten commented Sep 13, 2024

any updates on this?

@TheQue42
Copy link
Author

Personally, although I havent had time to look into detail of this, I think it has already been fixed. Before, I always started a shell in a freshly created frigate container, and manually modified nginx's log-config. But I think that I dont have to do this any more, since .14 or something...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix/Feature: Nginx respect logger configuration (sometimes) skrashevich/frigate
5 participants
@insound @NickM-27 @pissten @TheQue42 @LeoI5