You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As developers tracing user activity, such as after bugs, we want to be able to track the user actions easily. Cloud.gov records router logs with ip address (remote addresses), however, it takes a while to correlate that ip address to the corresponding username. It would be great if we had our own "router" logs that included user info to speed up log tracing time on stable
Acceptance criteria
the below should only apply in production (to avoid excess logs)
when a a url is entered in our system it is logged with the following
(if user is in) email address
remote address of the request
request path
(all of the above should be on one log line to keep it readable and easily skimmed
Additional context
example for inspiration but not identical to what we want
Links to other issues
No response
The text was updated successfully, but these errors were encountered:
Issue description
As developers tracing user activity, such as after bugs, we want to be able to track the user actions easily. Cloud.gov records router logs with ip address (remote addresses), however, it takes a while to correlate that ip address to the corresponding username. It would be great if we had our own "router" logs that included user info to speed up log tracing time on stable
Acceptance criteria
Additional context
example for inspiration but not identical to what we want
Links to other issues
No response
The text was updated successfully, but these errors were encountered: