I'd like to run journalctl-proxy on a publicly accessible server, but would like to restrict access to the listing of available services to "non-sensitive" services. Specifically, I am interested in only exposing the journalctl logs for one or two related services.
It would be nice to have a config option or command-line argument that allows defining one or more (maybe using regex) patterns for service names to show in the dropdown list.
This could also be combined with some level of authentication/authorization, to prevent un-authorized access to potentially sensitive logs. Ideally, some level of account/role management to restrict which services are exposed to which users/roles (system admins could view all logs, but service admins could only view their own services).
I'd like to run journalctl-proxy on a publicly accessible server, but would like to restrict access to the listing of available services to "non-sensitive" services. Specifically, I am interested in only exposing the journalctl logs for one or two related services.
It would be nice to have a config option or command-line argument that allows defining one or more (maybe using regex) patterns for service names to show in the dropdown list.
This could also be combined with some level of authentication/authorization, to prevent un-authorized access to potentially sensitive logs. Ideally, some level of account/role management to restrict which services are exposed to which users/roles (system admins could view all logs, but service admins could only view their own services).