There is a tight integration with the "Dvls Scheduler Service" and configuration of external Syslog server, so much so that when we had an outage this week on our syslog server (managed by another team) we experienced a production outage of Devolutions and Devolutions PAM.
Is there a way to setup notifications if we are having issues or to not have such tight integration with this service to avoid outages outside our teams control?
I am open to any suggestions to ensure more robust service for our customers.
As an FYI, we have changed our syslog server configuration to utilize UDP protocol now. If this will allow for less of a reliance of the service "having" to be available and not cause this type of outage, please let us know.
Hello,
Thank you for reaching out to us on this matter. I'm sorry to hear that. Having a syslog server down should not create an outage with Devolutions Server. We will investigate this and keep you posted once we have an update.
Best regards,
François Dubois
Hello,
For your information, we have opened a ticket in our backlog. We will investigate this as soon as possible and post back here once we have an update.
Best regards,
François Dubois
Hello,
For your information, I moved the thread in support section since it is something that should work.
Best regards,
François Dubois
Hello,
Thank you for reaching out!
My name is William and I'm here to assist you in any way I can.
An internal ticket has been opened with our development team to assess potential solutions. However, it's important to note that we are unable to provide a precise release date due to the intricate nature of our release process, which encompasses Build, Quality Assurance, and Release stages. Rest assured that we will be in touch as soon as we have an update to provide.
In the meantime, if you'd like to stay updated on the latest fixes, improvements, and release notes, you can access our Release Notes page by following the link below:
Devolutions Server - https://devolutions.net/server/release-notes/.
As for the notification, you can configure a notification subscription but based on the issue, I fear that the scheduler service will not be able to send the notification since it might get cought on heartbeat failure from the syslog server. But this is something that you would need to try.
Here is our documentation on configuring the notification subscription:
Feel free to reach out if you have any questions or need further clarification.
Best regards,