topic Re: Replicate UI logs in Qlik Replicate

Replicate UI logs

Raviraj — Wed, 24 Jan 2024 22:16:06 GMT

I want to check the replicate UI logs where some change in the settings is recorded. For example, in End point connections we have set up log back up and selected option to Prioritize online logs setting. For some reason the setting got dropped and it went back to Online logs.

Not sure who changed it or how it got changed.

Re: Replicate UI logs

DesmondWOO — Thu, 25 Jan 2024 02:30:56 GMT

Hi @Raviraj ,

Replicate UI does not possess audit feature. Please check if the Qlik Enterprise Manager(QEM) can provide the needed functionality. However, such as "selected option to Prioritize online logs setting", QEM does not document each step at such a detailed level.

Regards,
Desmond

Re: Replicate UI logs

Heinvandenheuvel — Thu, 25 Jan 2024 14:08:30 GMT

Your best bet is probably to have a weekly or even daily script to perform exportrepository to capture a date-time stamped JSON capture of all tasks, all endpoints. It's useful as backup and change control.

Just collect in a zip file is probably good enough.

But you could go crazy and after an fresh export compare against the prior version(s). If 'the same' except for the time/date stamp then you can delete that prior version. If different send a quick Email with change summary (task name, or endpoint name perhaps, to some person or group to decide whether the change was expected or not. A script could also be set up to retain the last 10 daily ones always, a weekly snapshot for 10 weeks, and a monthly snapshot for ever.

Hein

Re: Replicate UI logs

deepaksahirwar — Fri, 26 Jan 2024 13:19:36 GMT

Dear @Raviraj ,

I have understood your exact query and you wish to inspect the changes happened on the application via logs.

Replicate UI logs are files that record the activities and events of the Qlik Replicate user interface. They can help you troubleshoot issues, monitor performance, and audit changes in the replication settings.

To check the replicate UI logs, you need to access the log directory of the Qlik Replicate server. The default location of the log directory is:

On Windows: C:\ProgramData\Qlik\Replicate\log

On Linux: /var/opt/attunity/replicate/log

You can also change the log directory location by editing the DataDirectory parameter in the attreplicate.ini file.

To find out who or what changed the settings in the End point connections, you can look for the following entries in the replicate UI logs:

User <username> changed the endpoint <endpoint name> configuration

User <username> executed the command <command name> on the endpoint <endpoint name>

Endpoint <endpoint name> configuration was changed by <source>

The <source> can be either API, CLI, or UI.

If you have any other queries, feel free to ask me. 😊

If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer

Best Regards,

Deepak

Re: Replicate UI logs

Raviraj — Mon, 29 Jan 2024 22:09:22 GMT

Hi Deepak,

Thanks for your reply. Somehow I dont see the logs in the path you have mentioned and also cant find the attreplicate.ini file anywhere in the Attunity install folder. Not sure if I am missing something

Thanks

Raviraj

Re: Replicate UI logs

Raviraj — Mon, 29 Jan 2024 22:10:38 GMT

Hi Desmond

As I understand it , QEM will only monitor the health status of Replicate and compose. Does it have ability to check for the configuration changes within Replicate and compose?

Thanks

Raviraj

Re: Replicate UI logs

Dana_Baldwin — Mon, 29 Jan 2024 22:53:09 GMT

Hi @Raviraj

QEM does have an audit capability which you can read about here: Creating an audit trail | Qlik Enterprise Manager Help

I believe it can only audit changes made within the QEM tool, not if they were made directly in Replicate/Compose.

Hope this helps,

Dana

Re: Replicate UI logs

Raviraj — Mon, 29 Jan 2024 22:55:57 GMT

thanks Dana for the link. yes I am looking for Audit of the changes made with in replicate UI for the END POINT Connections.

Re: Replicate UI logs

DesmondWOO — Tue, 30 Jan 2024 02:19:16 GMT

Hi @Raviraj ,

In my previous response, the attached link is about QEM's Creating an Audit Trail. You can export audit information to a csv file.

Let's say you modify the endpoint. You would find following information:

Request Action: putdatabase
Payload: Your endpoint details. (Copy the link and paste it to the browser.)

The "Payload" does not specify which parameter has been modified. It may be necessary to compare historical records to discern the differences.

Regards,
Desmond

Re: Replicate UI logs

Dana_Baldwin — Tue, 30 Jan 2024 16:57:54 GMT

Hi @Raviraj

Please read the documentation at the link I posted for more information.

Thanks!

Dana

Re: Replicate UI logs

Raviraj — Tue, 30 Jan 2024 17:50:28 GMT

Thanks Desmond, I have gone though the logs and downloaded the Audit from QEM as CSV. Seems it will only contain the modifications that were done from QEM UI. In my aspect the change to END Point was from Qlik Replicate UI , that might be the reason its not showing in QEM Audit.

As understood , seems there is no Audit for the changes done in replicate UI.

Re: Replicate UI logs

DesmondWOO — Wed, 31 Jan 2024 02:29:35 GMT

Hi @Raviraj ,

You are right. If changes are made in the Replicate UI or through other methods, such as modifying the JSON file, QEM will not be able to audit.

Regards,
Desmond

Re: Replicate UI logs

Heinvandenheuvel — Wed, 31 Jan 2024 03:46:10 GMT

@DesmondWOO >> The "Payload" does not specify which parameter has been modified. It may be necessary to compare historical records to discern the differences.

As per my earlier reply. It seems you are stuck with EXPORT JSON such that you can at least know what has changed, even though you would not know who nor when.

Your regular change control process should of course cover all details - who what when, but out of those I find 'what' most important for support situation. You can always blame the dev team. 🙂

@DesmondWOO >> You are right. If changes are made in the Replicate UI or through other methods, such as modifying the JSON file, QEM will not be able to audit

Thanks for confirming this terrible news. How dare Qlik call this 'audit'? It's just a joke imho.