On Wed, Jan 22, 2020 at 1:41 PM Nick Couchman <[email protected]> wrote:
> On Tue, Jan 21, 2020 at 2:36 AM rolando58 <[email protected]> wrote: > >> Hi >> >> With a bit of digging I have rediscovered the logging paths. Its apparent >> that the logs are there and date stamped correctly. However I was hoping >> to >> find more meaningful information about user sessions in guacd, but the >> logging obscures the user name with >> >> " INFO:\u0009User \"@bd3a7c1a-a7b...etc...etc \" disconnected (0 users >> remain)" >> >> I went looking for the user reference to match but could find nothing, >> even >> in the mariadb database. Is the a way to match up the details of guacd >> with >> the plain text user name? >> >> > A couple of things... > 1) You can put guacd into debug mode using the "-L debug" option when > starting guacd. This will probably give you more detailed information and > help you in getting the information you need. > 2) guacd has no "knowledge" of users that log in from the Guacamole Client > - it basically just accepts a connection request from Guacamole client with > any of the connection parameters and facilitates that connection. Also, > the connection/user ID identified in guacd are ephemeral and are not stored > or logged anywhere. The only way to track between the two is to look at > logs (debug mode - see the manual) from Guacamole Client and correlate the > entries with guacd logs. The UUID should be logged in both places, so you > should see messages from both of those sources with the connection/user ID. > Perhaps this should be changed. While guacd definitely shouldn't be aware of webapp internals, logs frequently need to be correlated, and this is difficult in large deployments where timestamps become ambiguous. It would be helpful for guacd to be able to receive some sort of arbitrary contextual identifier that could be used to correlate guacd's logs with the logs of the service using guacd. For example, the webapp could generate a UUID for each request, include that UUID in any log messages related to that request, include that UUID in the error JSON of any REST failure for that request, and pass the UUID to guacd for inclusion in guacd's logs if the request establishes a connection. - Mike
