Gateway token generation should be a debug log instead of information.

This feature has been implemented in version 2025.3.5.0
Implemented

Gateway token generation should be a debug log instead of information.

7 votes

avatar

Hi,

Every time a user or the scheduler service accesses the Devolutions Gateway, an entry is created in the data source logs.

Currently, this entry is logged as type "Information", but it should instead be logged as type "Debug".

When the Gateway is heavily used, either by a customer or the PAM module, this behaviour generates a large number of logs. As a result, the data source logs become harder to read and navigate. Since this information is only useful in debugging scenarios, it would be better suited under the "Debug" log level.

Here’s an example of the log entry I am referring to:


Please let me know if you need any additional details.

Best regards,

Marc-Antoine Dubois

784b45c2-614b-4b34-b031-cc6f8b0f9c57.png

All Comments (2)

avatar

Hello,

Thank you for the suggestion. You are right, logging that information at the debug level should be sufficient. We will fix it and let you know once it is completed.

Best regards,

François Dubois

avatar

Hello,

This issue has been fixed and will be available in our version 2025.3.5.0 or higher.
Thank you for your patience.

Best regards,

Marc-Andre Bouchard

This feature has been implemented in version 2025.3.5.0