IT Monkey:    
Effective January 30, 2018 this app has been retired by Cireson. Cireson will no longer provide future feature updates, security patches, or support. However, the functionality you know and love has been enhanced and integrated into the new True Control Center.

To get the most of out of your System Center investment and to ensure compatibility with other software applications and systems, we recommend you take advantage of the True Control Center. Take it for a test drive in our online demo lab or request a free 30-day trial.

Is there a mechanism that prevents the protocol(s) from becoming too large?

Is there a mechanism that prevents the protocol(s) from becoming (e.g. "Cireson TickerApp.log") too large?

Best Answer

Answers

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭
    Disclaimer not using the App Ticker. However in general all the logging I have run into from the whole catalog has needed me to add controls for file size and volume. 
    Meaning on all log locations I have two scheduled tasks for PowerShell to 
    One for the running logs to rename the current log with the date so the application will start a new one. (This provide me one running log for each day)
    Two for the volume of logs a script that delete any log older then 30 days. 
    With these two scripts my log folders keep only 30 days so disk space is not consumed and the running logs do not exceed to big files sizes.
    HTH
This discussion has been closed.