File Size in MegaBytes (LOGFileSizeMB)
This parameter is inactive by default and should only be activated after you have inactivated the LOGFileSize parameter. When activated, this parameter displays the size of the file you are monitoring in megabytes. The LOGFileSize parameter displays the size of the file you are monitoring in bytes. When the number that represents the file size in bytes exceeds 10 digits, the number no longer displays correctly. If this is an issue in your environment, inactivate the File-Size-in-Bytes-LOGFileSize parameter, and activate the parameter.
Default action taken by PATROL
None.
Recommendations
This is an important parameter to monitor because log files usually grow continuously and can often grow large enough to cause problems before you remember to purge old log data.
If a log file grows too large, you should delete or archive the file to reclaim lost disk space. You may want to create a recovery action that deletes or archives log files once they grow to a certain size.
Range thresholds
Because the size of log files and the amount of free disk space varies with each system, no range thresholds have been set by default. Determine a maximum log file size and use it to set a range threshold for your system.
BMC PATROL properties
Property | Default value |
---|---|
Application class | LOGMON |
Command type | not applicable |
Platform | all |
Icon style | graph |
Unit | number of megabytes |
Border range | undefined |
Alarm1 range | undefined |
Alarm2 range | undefined |
Scheduling (poll time) | inherits poll time of collector |
Active at installation | yes |
Parameter type | consumer |
Value set by | not applicable |
TrueSight/ Unknown macro: confluence_includeplus.
properties
Property | Default value |
---|---|
Monitor type | Log Monitoring File |
Key Performance Indicator | No |
Monitor for abnormalities | Yes |
Graph by default | No |
Availability | No |
Response time | No |
Normal distribution | No |
Statistical | Yes |