Suggest an Idea

[Zareh_T]

In Qlik Sense February 20 release, the Qlik Centralized Logging Service handles communication outages with PostgreSQL by retrying three times to establish the connection and displays an error if unsuccessful. Communication outages with PostgreSQL can occur for a number of reasons and are not always recoverable in the limited retries of three times.
For example if the repository database is taking longer time than the total  time of 3 retries before it is up and running.
A suggestion is to restart the centralized logging service after 3 retries, then loop the same 3 retries / restart until communication is established with repository Postgres repository database.

[Thomas_Hopp]

Hi @Zareh_T and thank you for posting this idea. I'm closing it as declined as we decided to not use the centralise logging capability long term wise. We will deliver over the next couple of releases improvements in how you can collect and pull together all the log data you need in a very easy way, but the centralise logging itself won't be changed anymore. You will see those updates as part of our Releases in 2021. But at the same time we are not removing it right away from the product. First change you probably have noticed already, it is no longer selected by default when you install a new QSE Server.