DefGuard / defguard

The only _real_ 2FA MFA WireGuard Enterprise VPN with build-in SSO, hardware keys management and more!
https://defguard.net
Other
1.12k stars 35 forks source link

GATEWA&CORE logs should provide more INFO/business details #601

Closed teon closed 1 month ago

teon commented 6 months ago

A lot of users state that logs do not provide any information. For example latest bugs with logs that do not state anything:

defguard-gateway  | [2024-03-24T22:56:22Z ERROR defguard_gateway::gateway] Couldn't retrieve gateway configuration, retrying: status: Unavailable, message: "error trying to connect: received corrupt message of type InvalidContentType", details: [], metadata: MetadataMap { headers: {} }

or here - 2FA fails and no info..

2024-03-24T17:37:31.440129Z DEBUG http_request{method=POST path=/api/v1/client-mfa/start}: tower_http::trace::on_response: finished processing request latency=7 ms status=200
2024-03-24T17:37:38.499463Z DEBUG http_request{method=POST path=/api/v1/client-mfa/finish}: tower_http::trace::on_request: started processing request
2024-03-24T17:37:38.499643Z  INFO http_request{method=POST path=/api/v1/client-mfa/finish}: defguard_proxy::handlers::desktop_client_mfa: Finishing desktop client authorization
2024-03-24T17:37:38.504330Z DEBUG defguard_proxy: RPC message received CoreResponse { id: 46, payload: Some(ClientMfaFinish(ClientMfaFinishResponse { preshared_key: "gjHMXuW5UbldOdN6/asdfasdfasdf=" })) }
2024-03-24T17:37:38.504403Z DEBUG http_request{method=POST path=/api/v1/client-mfa/finish}: tower_http::trace::on_response: finished processing request latency=4 ms status=200