Agreed that would be helpful. But even more helpful would be finally logging a unique identifier for a connection and to tie logs from guacd to the guacamole app ☹️
--Steve From: Brad Turnbough <[email protected]> Date: Tuesday, July 14, 2026 at 2:26 PM To: [email protected] <[email protected]> Subject: Guac Logging This Message Is From an External Sender This message came from outside your organization. Report Suspicious<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/KGKeukY!vwQf06ZtD6YgJRdwH4-k180UfIUBzWB9qGiOy52bk5PKBqB6X2cRq4JI96VE9Ht1GZl_rI7-gzG7Yk16VleSC-UbyIFKTcJCt5h9pILdEGleqbKum3WPZPl3-W8TfOiCf58ku4n9tlOqUoTP$> I have logging working pretty well, but there is one thing that still bothers me. For example: Jul. 14, 2026 1:22:38.911 2026-07-14T06:22:37,517Z [https-openssl-apr-443-exec-6] INFO o.a.g.tunnel.TunnelRequestService - User "USERABC" connected to connection "123". Jul. 14, 2026 1:22:38.911 2026-07-14T06:22:37,524Z [https-openssl-apr-443-exec-25] INFO o.a.g.tunnel.TunnelRequestService - User "USERABC" connected to connection "132". Can guac be configured to log the connection name in addition to the connection number of “123” or “132” I have the skills to write the query to get the info out of the database manually, but I figured the logger should at least log the connection name for immediate analysis purposes. Thanks, Brad Thank you, Brad Turnbough Senior Technology Analyst [cid:Backlund-Investment-logo_20ce9d6e-04b9-4d73-9d17-cfc69decf4cc.gif] P: 309.272.2739 www.betterbanks.com<https://urldefense.com/v3/__http://www.betterbanks.com/__;!!KGKeukY!xcmGJK-IZseQDKssFP5KaONgdDQgJaioArmBt6dmONhg7iTIifwlCJcWhqnECmYsbWXuZGfbP7YEIZ2FK02PtVz0ZvmIJPfq7ZE$> www.statestreetbank.com<https://urldefense.com/v3/__http://www.statestreetbank.com__;!!KGKeukY!xcmGJK-IZseQDKssFP5KaONgdDQgJaioArmBt6dmONhg7iTIifwlCJcWhqnECmYsbWXuZGfbP7YEIZ2FK02PtVz0ZvmIUy-rxqg$> NOTICE: The information contained in this email and any document attached hereto is intended only for the named recipient(s). If you are not the intended recipient, nor the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this transmittal or its attachments is strictly prohibited. If you have received this transmittal and/or attachments in error, please notify me immediately by reply e-mail and then delete this message, including any attachments.
