starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #338] Syslog destination #297

New issue

Closed

opened 2026-02-26 06:32:07 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:32:07 +03:00

Owner

Originally created by @m1cypher on GitHub (Mar 25, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/338

I would like to have the audit logs and access logs (HTTP/HTTPS access combined) to be sent to my SIEM for graphing and other access.

If I am missing this somewhere, I am sorry.

I am using the docker version, with unraid.

I should also note, you have a made a great item. Thank you.

Originally created by @m1cypher on GitHub (Mar 25, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/338 I would like to have the audit logs and access logs (HTTP/HTTPS access combined) to be sent to my SIEM for graphing and other access. If I am missing this somewhere, I am sorry. I am using the docker version, with unraid. I should also note, you have a made a great item. Thank you.

kerem

2026-02-26 06:32:07 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:32:08 +03:00

Author

Owner

@vsc55 commented on GitHub (Apr 12, 2020):

Hi,
To achieve this you have to edit the Host, go to the "Advanced" tab and in "Custom Nginx Configuration" add the following configuration:

access_log syslog:server=192.168.1.100:514,tag=nginx,severity=info combined;
error_log syslog:server=192.168.1.100:514,tag=nginx,severity=debug;

The good thing would be to be able to configure it in some general nginx configuration so you don't have to add it on each host.

More Info:
https://docs.nginx.com/nginx/admin-guide/monitoring/logging/

@vsc55 commented on GitHub (Apr 12, 2020): Hi, To achieve this you have to edit the Host, go to the "Advanced" tab and in "Custom Nginx Configuration" add the following configuration: ``` access_log syslog:server=192.168.1.100:514,tag=nginx,severity=info combined; error_log syslog:server=192.168.1.100:514,tag=nginx,severity=debug; ``` The good thing would be to be able to configure it in some general nginx configuration so you don't have to add it on each host. More Info: https://docs.nginx.com/nginx/admin-guide/monitoring/logging/

kerem commented

2026-02-26 06:32:08 +03:00

Author

Owner

@m1cypher commented on GitHub (Feb 22, 2021):

Hi,
To achieve this you have to edit the Host, go to the "Advanced" tab and in "Custom Nginx Configuration" add the following configuration:
access_log syslog:server=192.168.1.100:514,tag=nginx,severity=info combined;
error_log syslog:server=192.168.1.100:514,tag=nginx,severity=debug;
The good thing would be to be able to configure it in some general nginx configuration so you don't have to add it on each host.

More Info:
https://docs.nginx.com/nginx/admin-guide/monitoring/logging/

So I never noticed that you replied to this, but I want to make sure I understand. Do I have to do this for each host that I created? Or is it a universal configuration?

@m1cypher commented on GitHub (Feb 22, 2021): > Hi, > To achieve this you have to edit the Host, go to the "Advanced" tab and in "Custom Nginx Configuration" add the following configuration: > > ``` > access_log syslog:server=192.168.1.100:514,tag=nginx,severity=info combined; > error_log syslog:server=192.168.1.100:514,tag=nginx,severity=debug; > ``` > > The good thing would be to be able to configure it in some general nginx configuration so you don't have to add it on each host. > > More Info: > https://docs.nginx.com/nginx/admin-guide/monitoring/logging/ So I never noticed that you replied to this, but I want to make sure I understand. Do I have to do this for each host that I created? Or is it a universal configuration?

kerem commented

2026-02-26 06:32:08 +03:00

Author

Owner

@vsc55 commented on GitHub (Feb 22, 2021):

Hi @odin-bb,

You have 2 options:
Option 1: Add it on all vhost.

Option 2: Add it to a custom file (this is the one I use).
If in any vhost you want to use another configuration such as another server, you only have to add said configuration in "Advanced" of the vhost.

With the following example we configure in all the vhosts that "error_log" only sends the error messages to the syslog00 server, and that the debug.domain.local vhost sends all the messages to the syslog01 server.

vi %path docker%/data/nginx/custom/server_proxy.conf
error_log syslog:server=syslog00.domain.local:514,tag=nginx,severity=error;
access_log syslog:server=syslog00.domain.local:514,tag=nginx,severity=info combined;

Advanced config vhost "debug.domain.local":

error_log syslog:server=syslog01.domain.local:514,tag=nginx,severity=debug;

@vsc55 commented on GitHub (Feb 22, 2021): Hi @odin-bb, You have 2 options: Option 1: Add it on all vhost. Option 2: Add it to a custom file (this is the one I use). If in any vhost you want to use another configuration such as another server, you only have to add said configuration in "Advanced" of the vhost. With the following example we configure in all the vhosts that "error_log" only sends the error messages to the syslog00 server, and that the debug.domain.local vhost sends all the messages to the syslog01 server. ``` vi %path docker%/data/nginx/custom/server_proxy.conf error_log syslog:server=syslog00.domain.local:514,tag=nginx,severity=error; access_log syslog:server=syslog00.domain.local:514,tag=nginx,severity=info combined; ``` Advanced config vhost "debug.domain.local": ``` error_log syslog:server=syslog01.domain.local:514,tag=nginx,severity=debug; ```

kerem commented

2026-02-26 06:32:08 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 31, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Mar 31, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:32:08 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 10, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (May 10, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#297

No description provided.

Rows
Columns