Hello,
While working on a SIEM integration for Devolutions, I’ve encountered several limitations regarding the Get-HubSiemLogs command.
Since the solution currently cannot directly connect to a SIEM for live log forwarding, I started exploring possible automation approaches and noticed several issues related to how logs are generated and structured.
Identified issues :
The Data field appears to be encrypted, and no information is available about its content or decoding process.
The UserIpAddress field always returns the class name Devolutions.Hub.Clients.LogIpAddress instead of the actual IP address.
There is no clear way to identify the user who triggered the event — only their internal account ID is shown.
There is no log severity level (e.g., INFO, WARN, ERROR), which makes it difficult to filter or prioritize log events.
Would it be possible to consider improving the log structure to address the points listed above?
A dditional feature requests :
Real-time log streaming :
It would be very useful to have a feature similar to the Linux tail -f command, allowing continuous and real-time log monitoring. Currently, the only available options are “Weekly” and “Daily” log packages, which are not practical for active monitoring of a critical service like Devolutions Hub.
Log forwarding capability :
For the SaaS version, could you add an option to forward logs to an external application using an authentication key? In our case, we use Sekoia, which doesn’t have a native intake for Devolutions yet — but we could build one, provided we can receive logs directly from your platform.
Thank you in advance for your attention to these points and for considering these improvements.
Please let me know if you need additional details or examples from my current integration tests.
Kind regards.