Skip to main content
Submitted

Automated, regular cleanup of execution logs

  • December 18, 2019
  • 3 replies
  • 3 views

Forum|alt.badge.img

It would be great to have the ability to configure TX to automatically clean execution logs older than N days/weeks, on a rolling basis.

For example, a housekeeping process that is run once per day, at a time the user chooses: user choice of time would important because in my organization, we actually shut down our TX virtual machine (on Azure) for 8 hours each night. 

Another potentially-useful behavior configuration would be whether Successful logs should be treated differently to Failed logs. We might want to keep information about failures for longer than successes. 

The benefit of this automation would be to prevent TX users having to follow these steps: https://support.timextender.com/hc/en-us/articles/115004530803-Size-issues-with-your-repository-Clean-up-the-logs-and-get-more-space

The comments on that article already indicate support for this request. 

This is related to: https://support.timextender.com/hc/en-us/community/posts/360005494483-Repository-Cleanup, but I think it is a different request because that issue is not discussing automation, but an improved user-interface. 

3 replies

Forum|alt.badge.img
  • Author
  • New Participant
  • December 18, 2019

Potential short-term half solution as suggested in the KB article: TimeXtender staff could provide a vetted SQL script that performs the correct DELETE statements (and whatever else is necessary), which us users could run manually in a SQL client (SSMS, etc) or schedule in a SQL Agent job. 

Building this into the UI would clearly be better but I think many of us would be fairly happy with a script approach. 


Forum|alt.badge.img
  • Known Participant
  • December 19, 2019

Agreed. Same thing with leftover synchronization results from deleted projects. These can inflate your db size also. TX support kindly gave us a script to clean these up manually but it is of course "at our own risk".

I'm going to shamelessly promote my suggestion for a separate logging database again :-):

https://support.timextender.com/hc/en-us/community/posts/115017825683-Row-Count-execution-time-logging-to-external-database


Forum|alt.badge.img
  • New Participant
  • March 23, 2020

With all the up votes this suggestion has received, I'm sure it's on R&D's radar :-)