Feature: Direct SSH connection launch from host list
First, I'd like to commend the team on this excellent project. The implementation is solid and the UI is exceptionally well-designed.
I understand the rationale behind not including automated patching functionality at this time. However, I'd like to propose a feature enhancement that could improve workflow efficiency when managing outdated hosts.
Feature Request: Direct SSH Connection Launch
Would it be feasible to add a button or link in the outdated hosts view that would initiate an SSH connection directly to the selected host? This could be implemented as:
- A single-host action: Allow launching an SSH session to individual hosts from the list view
- A bulk action: Enable selecting multiple hosts requiring updates and opening concurrent terminal sessions to all selected hosts
Use Case:
This would streamline the workflow for administrators who need to manually access systems for updates, reducing the friction between identification and remediation of outdated hosts.
I believe this enhancement would complement the monitoring capabilities while respecting the project's current scope regarding automated patching.
Thank you for considering this request.
5 Comments
@9technologygroup, small hint, you can find this feature implemented in https://github.com/openrport/openrport. It has a MIT-License, so maybe it could make sense to use portions of it.
Sounds good.
My suggestion was more like a bandaid while you get there but the more I tought about it the less sense it made.
I was originally thinking a link to spawn the default terminal but even using the
ssh://url would require for you to know the ssh username innorder to craft the correct URL.You can close/scratch this request
I think is much more K.I.S.S. to have the ability on the web ui to make custom button (aka links) in the various pages of the interface (like "update now" on the host's detail page or "update all" on the host list) . This is rather generic: button are just links and you could customize them as you want. Essential is the usage of macros (eg: $host in the host's detail point to hostname of the agent)
Sounds good.
My suggestion was more like a bandaid while you get there but the more I tought about it the less sense it made.
I was originally thinking a link to spawn the default terminal but even using the ssh:// url would require for you to know the ssh username innorder to craft the correct URL.
You can close/scratch this request
Hey @jaas666 - Thank you for your appreciation on this project.
It's made me question the purpose of life when certain things are not working and other times made me extremely pleased when things are working right !! :D
Your suggestion is quite valid though we have a few ways of doing this.
I am going to research into this seperately, because we have come up with a design on how we wish to leverage Ansible for Patch Management without the need of SSHing from PatchMon.
Saying this, I'm now researching on leveraging the persistent WSS (Web Socket Secure) connection to proxy ssh connection and have a terminal window within PatchMon for access.
PatchMon server can generate the ssh key pair and the Go Agent can install the public key in the authorized_keys file and it will then work fine ... That's my initial plan though I need to test / build / research and code it in.
Done in 1.4.0. Not only this but you have the ability to SSH into the server through the connected websocket through reverse SSH tunneling !
It will be out soon <1 week but this has been done and working flawlessly.
<img width="1262" height="389" alt="Image" src="https://github.com/user-attachments/assets/c53ccfc5-ad54-4a4d-911a-188bd62b5ef8" />
Along with an ai assistant that can be used :
<img width="1603" height="847" alt="Image" src="https://github.com/user-attachments/assets/3ba956a6-5738-423a-a981-27f70ee875bc" />