Open tunloop opened 2 months ago
plugins can add ship their own configurations when needed, I don't think there's much to add from core's perspective here. (some plugins use this already https://github.com/opnsense/plugins/blob/master/www/caddy/src/etc/syslog-ng.conf.d/caddy.conf).
Selections for remote selection can be hooked as well (https://docs.opnsense.org/development/backend/legacy.html#syslog)
Understood. I was hoping there would be apetite for expanding it from a first party perspective, but plugins are great for this.
Just out of curiosity, what is the threshold for when OPNsense core will add functionality itself?
when a facility is missing or incomplete or when it adds clear functionality which we also believe should be configurable via the gui.
Important notices
Is your feature request related to a problem? Please describe.
Currently, with community plugins like Adguard Home, non-standard log files cannot be ingested into syslog-ng (for remote logging) without creating the syslog-ng conf files manually through SSH. This is not a perfect solution as the logging configuration for a file source in syslog-ng would not be backed up by OPNsense.
Additionally, if one wanted to add a custom template for a different log format, using syslog-ng's
template
feature, it would also have to be done through SSH and have no backup.Describe the solution you like
I'd like to see the GUI System->Settings->Logging configurations expanded to include more of syslog-ng's powerful features like file sources and templates.
Additional context
Obviously, there are a lot of different ways to configure syslog-ng. I am not asking for all of them to have an option in the GUI, just important ones like file sources.
I would encourage anyone that comes across this and also wants a useful syslog-ng feature in the GUI to comment with it.