LogExpireAction
Determines how log files are handled when they exceed the maximum size. Type one of the following to determine how log files are handled when they exceed the LogMaxSizeKBs size:
| Option | Description | 
|---|---|
| Compress  | The log file's name is appended with a timestamp, compressed and saved in the log directory. By default, this is a ZIP file. Use the LogCompressionModeparameter to specify another compression format. | 
| Consecutive | The log file's name is appended with a number and saved in the log directory. When the next log file reaches its LogMaxSizeKBssize, it is appended with the next consecutive number. | 
| Datestamp | The log file's name is appended with a timestamp and saved in the log directory. | 
| Previous | The log file's name is appended with .previousand saved in the log directory. Every time a log file reaches itsLogMaxSizeKBssize, it is given the same postfix so that it overwrites the old log file. | 
| Day | Only one log file is created for each day and is appended with the current timestamp. Log files are archived after they reach the LogMaxSizeKBssize.NOTE: The  | 
| Type: | String | 
| Default: | Datestamp | 
| Required: | No | 
| Configuration Section: | Logging or LogStream or TaskName If you set this parameter in the LoggingandLogStreamsections, the setting in theLogStreamsection takes precedence for the specified log stream. | 
| Example: | LogExpireAction=Compress | 
| See Also: | LogCompressionMode LogFile LogMaxSizeKBs |