Obtain goaccess realtime HTML reports somewhere #146

Open
opened 2024-10-19 17:15:02 +00:00 by raito · 2 comments
raito commented 2024-10-19 17:15:02 +00:00 (Migrated from git.lix.systems)

We could run a goaccess long-lived program that threads through the NGINX access logs and update an HTML report to some protected location for admins.

We could run a goaccess long-lived program that threads through the NGINX access logs and update an HTML report to some protected location for admins.
winter commented 2024-10-20 19:42:26 +00:00 (Migrated from git.lix.systems)

Is it worth hooking into SSO for such a thing at this point? My initial thought would be to just do basic auth with some age-protected credentials for now.

Is it worth hooking into SSO for such a thing at this point? My initial thought would be to just do basic auth with some age-protected credentials for now.
raito commented 2024-10-21 07:41:35 +00:00 (Migrated from git.lix.systems)

Yeah, I'd just do oauth2-proxy and reuse the SSO for this.

A systemd service that runs the realtime daemon and push the HTML report in some location, NGINX pick this up and protect it via oauth2-proxy, we handle authorization via Keycloak roles for the rest.

Yeah, I'd just do oauth2-proxy and reuse the SSO for this. A systemd service that runs the realtime daemon and push the HTML report in some location, NGINX pick this up and protect it via oauth2-proxy, we handle authorization via Keycloak roles for the rest.
Sign in to join this conversation.
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: afnix/infra#146
No description provided.