Is it possible to configure Qlik Replicate to log to stdout instead of files without using the UI?
repctl.sh knows getserverlogger and setserverlogger commands, but they are undocumented. And I did not found a config file of a popular logging framework.
If it is not possible, this would be nice for containerization of the product. Currently one has to tail all logfiles, but not the rolled files.
Qlik Replicate stores task runtime information, including warning and error messages, in the task log files. There is currently no built-in mechanism to redirect the task log output directly to stdout.
If you could provide more details about your Replicate platform and the challenge you're trying to address, I'd be happy to help explore possible workarounds or alternative approaches that may meet your requirements.
Thanks,
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
We run Replicate in a container on Kubernetes. Containers must write their logs to stdout and stderr so that they can be captured by the Container runtime.
And I don't just talk about the Task logs. All logs should go to stdout.
But it would be much easier if the product would provide the possibility to configure stdout logging with a simple command to repctl or through a log configfile.
Unfortunately, the current versions of Qlik Replicate do not provide this capability or configuration option. If this functionality is important for your use case, I would recommend submitting a Feature Request (FR) through the Qlik Ideation portal:
No, it still doesn't work. Grey area with error dialog in the center.
In the browser's dev-tools I see a lot of async loaded resources with errors like "has been blocked by CORS policy: Request header field content-type is not allowed by Access-Control-Allow-Headers in preflight response" or even "403 (Forbidden)"
