You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Mike Jumper (Jira)" <ji...@apache.org> on 2026/10/05 10:58:00 UTC

[jira] [Reopened] (GUACAMOLE-2283) Runtime observability: add guacd process & thread naming.

     [ https://issues.apache.org/jira/browse/GUACAMOLE-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper reopened GUACAMOLE-2283:
------------------------------------
      Assignee: Mike Jumper

Reopening to abstract away thread titles a bit further and move the process title code into the internals of guacd (rather than provide that in the public libguac API).

I'm also going to adjust the process titling - the current format can confusingly resemble non-guac client processes, as with {{ssh someuser@somehost}}.

> Runtime observability: add guacd process & thread naming.
> ---------------------------------------------------------
>
>                 Key: GUACAMOLE-2283
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2283
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacd
>            Reporter: Bradley Bennett
>            Assignee: Mike Jumper
>            Priority: Major
>             Fix For: 1.6.1 [staging]
>
>
> Add process and thread naming to *guacd* to improve runtime observability and make active connections easier to identify in monitoring, profiling, and debugging tools.
> Process names
>  * vnc bb****tt@192.168.68.66:5900
>  * rdp bb****tt@192.168.238.152:3389
> Thread names
>  * conn-read
>  * display-wrk
> This makes it easier to correlate CPU, memory, and thread activity with specific connections when using tools such as top/htop, perf, gdb...
> For security reasons, user credentials are either not displayed (e.g. passwords) or obfuscated (e.g. username).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)