# Log File Analysis Tuning Parameters

The analysis tuning parameters are settings which control the generation of performance and configuration problems recorded in the Mitel Virtualization log files.

Contact Mitel Product Support if you wish to change the default value for an analysis tuning parameter.

Analysis Tuning Parameters | Description & Values
cluster:count | Specifies the number of events that must occur, in consecutive order, before a performance problem is reported for the ESXi host. For example, if the system detects five consecutive "out of bounds" events, an error will be reported. However, if the system detects four "out of bounds" events followed by an "in bounds" event, no error will be reported. Events are registered every 20 seconds. The default value is 5.0 (5 events).
file:rolldown | Specifies the numbers of days that log file events are kept before being deleted. For example, if you program the system to retain ten days worth of files, the first day's files will be deleted after ten days. The default value is 7.0 (7 days worth of log files).
host:cpu:hyperthread | If this tuning parameter is enabled, the system will check to determine whether the ESXi host uses hyperthreading. The default is 1.0 (Enabled). Note: This parameter can only report on Intel processors that support hyperthreading. It cannot report on AMD processors.
host:cpu:speed | Specifies the high/low setting of the CPU for the ESXi host. The default value is 2000.0 (2 GHz).
host:cpu:usage:average:percent | Specifies the amount of CPU capacity that the ESXi host can use, expressed as a percentage of the total amount available, before an event is registered. For example, if the virtual machine has four CPUs with 2 GHz processors, and you are running an application that requires 6 GHz (75% of capacity), an event will be registered. The default value is 50.0 (50%).
host:disk:maxTotalLatency:latest:second | Specifies the maximum amount of time, in seconds, that is permitted for a SCSI command to be issued by the guest operating system to the ESXi host hard disk. The default value is 0.04 (0.04 seconds).
host:disk:usage:average:megaBytesPerSecond | Specifies the amount of data, in Megabytes per second, that can be read from the ESXi host hard disk. The default value is 60.0 (60 MB).
host:mem:compressionRate:average:megaBytesPerSecond | Specifies the amount of memory, in Megabytes per second, that the ESXi host can compress. Compression can occur due to one of the following conditions: Memory leak Sizing of the virtual machine is not appropriate for its load, so it obtains resources from the host If the host is also compressing memory, there may be too many virtual machines powered up or the total amount memory used by the virtual machines is greater than that which the host is offering. The host is over-provisioned The default value is 0.0.
host:mem:overload | Specifies the point that the ESXi host is determined to be overloaded, expressed as a ratio of memory usage / memory capacity. For example, if five VMs are powered on, each using 2 GHz of memory, and the host has 8 GHz of physical memory, then the ratio is 2 + 2 + 2 + 2 + 2 / 8 = 1.25, which will cause an event to be registered. The default value is 1.2.
host:mem:swapused:average:megaBytes | Specifies the amount of memory, in Megabytes, that can be swapped from disk to memory. The default is 0.0.
host:mem:usage:average:percent | Specifies the amount of memory capacity that the ESXi host can use, expressed as a percentage of the total amount available, before an event is registered. For example, if the virtual machine has 4 GHz of memory, and you are running an application that requires 3 GHz (75% of capacity), an event will be registered. The default value is 75.0 (75%).
host:net:droppedRx:summation:number | Specifies the number of received packets that can be dropped at the network interface. The default value is 0.0.
host:net:droppedTx:summation:number | Specifies the number of transmitted packets that can be dropped at the network interface. The default value is 0.0.
host:net:usage:average:megaBytesPerSecond | Specifies the disk input/output rate, in Megabytes per second, that the ESXi host can use before an event is registered. The default value is 50.0.
host:vcpu:overload | Specifies the point that the ESXi host is determined to be overloaded, expressed as a ratio of vCPU usage / CPU capacity. For example, if five VMs are powered on, each having a 4 GHz vCPU, and the host has 16 logical cores, then the ratio is 4 + 4 + 4 + 4 + 4 / 16 = 1.25, which will cause an event to be registered. The default value is 0.79.
host:vmotion:enable | If this tuning parameter is enabled, the system will check to determine whether the ESXi host uses vMotion to facilitate the live migration of virtual machines from one physical server to another. The default is 1.0 (True).
host:window | Specifies the additional number of events that must occur before a problem is reported for the ESXi host. For example, if the cluster:count is set to 5.0 and this parameter is set to 2.0, then two additional "out of bounds" events must be detected before an error is reported. Events are registered every 20 seconds. The default value is 2.0.
vm:cpu:ready:summation:second | Specifies maximum amount the time, in seconds, that the virtual machine can be ready and then wait to be scheduled to run on the physical CPU(s). The default value is 2.0.
vm:cpu:usage:average:percent | Specifies the amount of CPU capacity that the virtual machine can use, expressed as a percentage of the total amount available, before an event is registered. For example, if the virtual machine has 2 CPUs, and you are running an application that requires 1 CPU, an event will be registered. The default value is 50.0 (50%).
vm:disk:maxTotalLatency:latest:second | Specifies the maximum amount of time, in seconds, that is permitted for a SCSI command to be issued by the guest operating system to the virtual machine hard disk. The default value is 0.02.
vm:disk:usage:average:megaBytesPerSecond | Specifies the amount of data, in Megabytes per second, that can be read from the virtual machine hard disk. The default value is 30.0.
vm:mem:swapped:average:megaBytes | Specifies the amount of memory, in Megabytes, that can be swapped from disk to memory. The default is 0.0.
vm:mem:usage:average:percent | Specifies the amount of memory capacity that the virtual machine can use, expressed as a percentage of the total amount available, before an event is registered. For example, if the virtual machine has 4 GHz of memory, and you are running an application that requires 3 GHz (75% of capacity), an event will be registered. The default value is 50.0 (50%).
vm:net:droppedRx:summation:number | Specifies the number of received packets that can be dropped at the network interface. The default value is 0.0.
vm:net:droppedTx:summation:number | Specifies the number of transmitted packets that can be dropped at the network interface. The default value is 0.0.
vm:net:received:average:megaBytesPerSecond | Specifies the maximum network data receive rate, in Megabytes per second. The default value is 25.0.
vm:net:transmitted:average:megaBytesPerSecond | Specifies the maximum network data transmit rate, in Megabytes per second. The default value is 25.0.
vm:net:usage:average:megaBytesPerSecond | Specifies the maximum network utilization (combined transmit and receive rates, in Megabytes per second). The default value is 50.0.
vm:snapshot | If this tuning parameter is enabled, the system will support virtual machine snapshots in ESXi. A snapshot preserves the state and data of a virtual machine at a specific point in time. The default value is 0.0 (False).