How does the archivedlogs cleansing works?

rawoeste — Thu, 25 Oct 2018 08:09:29 GMT

In the log monitor I've noticed the repository service doing some cleanup in the archivedlogs folder.

I can't seem to understand the logic ...

Example below involves data of one specific app. As you can see, the message indicates the app is reloaded every hour.

The cleansing happens every 6 hour and involves the last 6 files.

Date	Hour	Timestamp	Message
2018-10-24	19:00	2018-10-24 19:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_13_35_10.9AC6B748E741FB7C9266.log' for FileReference a5b02ae7-b875-48bb-bfa0-70a99993abb8 deleted
2018-10-24	19:00	2018-10-24 19:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_12_35_10.5946C763376AC69AC578.log' for FileReference e0a53e1c-6e55-442f-bfdb-3d77eabad2bc deleted
2018-10-24	19:00	2018-10-24 19:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_11_35_10.E6E24D26D42614D0EF15.log' for FileReference 3cbb943f-758f-4f63-b28c-a1ba894727e7 deleted
2018-10-24	19:00	2018-10-24 19:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_10_35_11.E0DCA97414609FC22ADA.log' for FileReference 9dc75ce0-7bb2-49f9-8ba6-61fe32bfa6b0 deleted
2018-10-24	19:00	2018-10-24 19:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_08_35_10.1BB257DADC7EC4B88566.log' for FileReference 20184369-3ed8-442e-b070-cf2f2dd87d2f deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_07_35_09.4DC6109E7996D32D38CF.log' for FileReference cfe7e513-57ab-4daa-b6cd-3b47fdd8acc9 deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_06_35_10.988BCFBC2F38F42337E6.log' for FileReference a722f13c-8670-4c0f-8485-797523c27642 deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_05_35_10.C68A822ACC7EB5E09AB3.log' for FileReference 695b2b63-8ca3-45df-9cd2-f6ca428f467e deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_04_35_10.004F200E6F2CAE1D1801.log' for FileReference 9e18b5d1-4de6-476d-b1e8-94093a6a1e4b deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_03_35_10.378AC9D79D541BB688CA.log' for FileReference 9577d29d-5987-44e5-b8dd-e8d8df1562e1 deleted
2018-10-24	13:00	2018-10-24 13:35:09	File with path '*serverpath*\Script\fcd271cb-cc0a-41af-b2ef-4ff7d00b30d2.2018_10_24_02_35_10.AC55A616A2E032B43F48.log' for FileReference 8a598eb7-3897-4c39-bb06-9652d08b6a70 deleted

Second example involves an app which is reload once a day. Cleanup seems to happen once a week.

Date	Hour	Timestamp	Message	ObjectName	ProxySessionId	UserId	Message Occurrences	Log Source	Log Entry
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_15_06_00_51.9DED8DC6B597B2157E1B.log' for FileReference cfd040ff-6faa-4ab0-ae9c-a7e6c6c6e4a8 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	389
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_18_06_00_32.F34454C9BA2019222C2A.log' for FileReference 6299a53e-4a40-4cb3-970d-909744e72b37 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	388
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_14_06_00_50.E8F2F2C95481ABBD994E.log' for FileReference 648487da-816e-45c7-8eea-2b436014bc86 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	387
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_17_06_00_38.F6FC0D1F96E1AB90DC23.log' for FileReference 97d9e37e-86e1-4cf9-bb57-38a37e3fe4a3 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	386
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_13_06_00_50.6B1790EA49B7F1C1BB39.log' for FileReference 3cc1b435-2a47-4933-a50a-df64c4e647d7 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	385
2018-10-22	8:00	2018-10-22 08:00:31	File with path '*serverpath*\Script\12a2a04c-45cf-45d9-a4e3-b2e1d7a439aa.2018_10_16_06_00_52.9175494962D57F3AACF9.log' for FileReference e14564a5-fe47-46e8-91e4-daad769c7b56 deleted	-	0	-	1	NTSRV50_Audit_Repository_2018-10-22T08.00.34Z.log	384

Is there a way to configure this more properly?

In C:\Program Files\Qlik\Sense\Repository\Repository.exe.config I've found this:

However, I don't see this correlating with the data from the log monitor ...

When does the cleanup happens and how does it determines what gets cleaned? Can we configure this in some way?

For example, I want to keep the logs of the first app for a longer period. What are the possibilities for accomplishing this?

Thanks!

Re: How does the archivedlogs cleansing works?

bgc — Fri, 26 Oct 2018 06:05:54 GMT

Hello Stef,

If this is for script logs then please check the support article - https://qliksupport.force.com/articles/000056032

Thanks

Tom Issac

Re: How does the archivedlogs cleansing works?

rawoeste — Fri, 26 Oct 2018 06:10:56 GMT

Thanks! Exactly what I needed !

topic Re: How does the archivedlogs cleansing works? in Management & Governance

How does the archivedlogs cleansing works?

Re: How does the archivedlogs cleansing works?

Re: How does the archivedlogs cleansing works?