Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
%Idle	Percentage of time the CPU was idle; the CPU had completed its tasks and has nothing to do.	Basic					Diagnostic
%Busy	Percentage of time the CPU was busy processing system or user requests; this metric includes CPU Stolen time.	Basic					KPI
%Stolen4	Usually, stolen time is the percentage of time a virtual CPU waits for a real CPU while the hypervisor is servicing another virtual processor.	Basic					KPI
%Nice	Percentage of CPU time spent on low priority processes.	Server Visibility					Advanced
System	Percentage of time the CPU was busy processing kernel code.	Server Visibility					KPI
User	Percentage of time the CPU was busy processing non-kernel code.	Server Visibility					KPI
IOWait	Percentage of CPU time spent waiting for an I/O request.	Server Visibility					KPI
%Irq	Percentage of CPU time spent servicing hardware interrupts.	Server Visibility					Diagnostic
%SoftIrq	Percentage of CPU time spent servicing software interrupts.	Server Visibility					Advanced
%Busy 95th Percentile2	The CPU %Busy percentage was at this level or lower 95% of the time.	Server Visibility					KPI
IOWait 95th Percentile2	The CPU %Busy percentage was at this level or lower 95% of the time.	Server Visibility					KPI

¹See Linux Kernel Processes.

²See Percentile Metric Reporting must be Enabled.

³See Default Monitoring Mode.

⁴See Stolen Times are Reported Differently.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Total (MB)	The total amount of memory.	Basic					KPI
Used %	The percentage of memory used.	Basic		4			KPI
Used (MB)	The amount of memory used.	Basic		4			Advanced
Free %	Percentage of free or unused memory available for processes.	Basic		4			Advanced
Free (MB)	The total amount of free or unused memory available for processes.	Basic		4			Advanced
Swap Free (MB)	The total amount of free swap space. Reported for each hierarchical group.	Server Visibility					Advanced
Swap Total (MB)	The total amount of allocated swap space. Reported for each hierarchical group.	Server Visibility					KPI
Swap Used (MB)	The amount of swap space used. Reported for each hierarchical group.	Server Visibility					Advanced
Swap Used %	The percentage of available swap space used. Reported for each hierarchical group.	Server Visibility					KPI
Swap Free %	Percentage of free swap space. Reported for each hierarchical group.	Server Visibility					Advanced
Pages Paged In 95th Percentile2	The paging-in rate to memory was at this level or lower 95% of the time.	Server Visibility					KPI
Pages Paged Out 95th Percentile2	The paging-out rate from memory was at this level or lower 95% of the time.	Server Visibility					KPI
Pages Swapped In 95th Percentile2	The swapping rate of pages from disks was at this level or lower 95% of the time.	Server Visibility					KPI
Pages Swapped Out 95th Percentile2	The swapping rate of pages to disks was at this level or lower 95% of the time.	Server Visibility					KPI

¹See Linux Kernel Processes.

²See Percentile Metric Reporting must be Enabled.

³See Default Monitoring Mode.

⁴See Stolen Times are Reported Differently.

The agent reports metrics for each disk partition and for disks in aggregate. Only mounted partitions and local partitions are reported.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
KB read/sec	The number of KB per second read from all disks and partitions.	Basic					Advanced
KB written/sec	The average amount of data per second written to all disks and partitions.	Basic					Advanced
Reads/sec	Number of read operations per second performed on all disks and partitions.	Basic					KPI
Writes/sec	Number of write operations per second performed on all disk and partitions.	Basic				5	KPI
Avg IO Utilization (%)	The average time spent processing read/write requests on all disks and partitions as a percentage of the total reported time window. Databases often report high disk I/O utilization due to frequent read/write requests. For example, if the agent detects read/write processing in 55 out of 60 seconds, the Avg IO Utilization for that minute is 92%. This metric does not measure the amount of available disk space or read/write request sizes.	Server Visibility					KPI
<partition> %CPU Time	The percentage of CPU processing consumed by a partition during read and write operations.	Basic (HardwareMonitor)6					Diagnostic
<partition>Avg Service Time (ms)	Time in milliseconds spent performing read and write operations across one partition.	Basic (HardwareMonitor)6					Diagnostic
<partition>Avg Queue Time (ms)	Time in milliseconds that a read or write request is in the queue before it gets processed across one partition.	Basic (HardwareMonitor)6					KPI
<partition>KB read/sec	The average amount of data per second read from one specific partition.	Basic (HardwareMonitor)6					Diagnostic
<partition>KB written/sec	The average amount of data per second written to one specific partition.	Basic (HardwareMonitor)6					Diagnostic
<partition>Reads/sec	Number of read operations per second performed on one specific partition.	Basic (HardwareMonitor)6					KPI
<partition>Writes/sec	Number of write operations per second performed on one specific partition.	Basic (HardwareMonitor)6				5	KPI
<partition>Space Available	The amount of unused or free disk space on a specific partition in KB.	Basic (HardwareMonitor)6		4			KPI
<partition>Space Used	The amount of used or unavailable disk space on a specific partition in KB.	Basic (HardwareMonitor)6		4			Advanced
<partition>Avg IO Utilization (%)	The average time spent processing read/write requests as a percentage of the total reported time window. Databases often report high disk I/O utilization due to frequent read/write requests. For example, if the agent detects read/write processing in 55 out of 60 seconds, the Avg IO Utilization for that minute is 92%. This metric does not measure the amount of available disk space or read/write request sizes.	Server Visibility					KPI
<partition>Avg read time (ms)	The average time in milliseconds required to service a read request by all disks or by one specific disk or across one partition.	Server Visibility	2				KPI
<partition>Avg write time (ms)	The average time in milliseconds required to service a write request across one partition.	Server Visibility	2				KPI
<partition>Queue Time 95th Percentile3	The queue time for read/write requests was this long or shorter 95% of the time for the reported time window.	Server Visibility					KPI

¹ See Default Monitoring Mode

² For some versions of Windows Server 2008 and Windows Vista, the Hardware Resources|Disks|<partition>|Avg Read Time (ms) and Hardware Resources|Disks|<partition>|Avg Write Time (ms) metrics will be reported as 0. This is due to a known bug with Windows. To resolve this issue, download the hotfix: https://support.microsoft.com/en-us/kb/961435.

³ See Percentile Metric Reporting must be Enabled.

⁴See Configure Disk Usage Metric Collection on Linux..

⁵See HardwareMonitor and JavaHardwareMonitor Calculate "Writes/Sec" Differently on AIX Machines.

• <MA-Home>/monitors/JavaHardwareMonitor : false
• <MA-Home>/monitors/HardwareMonitor : true
• <MA-Home>/extensions/ServerMonitoring/conf/ServerMonitoring.yaml : Set basicEnabled to true

Splunk AppDynamics Server Visibility Server Visibility retrieves the volume space metrics on POSIX systems using the df command. The volume metrics are reported across all listed volumes and for each volume at a specified mount point, such as "/boot". Only local volumes are reported.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Total (MB)	The amount of storage space available (used and free) across all listed volumes or at the specified mount point. On Linux, the space reserved for root is not counted in the available space.	Server Visibility					KPI
Free (MB)	The amount of unused or free space across all listed volumes or on the selected volume at the specified mount point. On Linux, the space reserved for root is not counted in the available space.	Server Visibility					Advanced (volume)
Used (MB)	The amount of storage space in use across all listed volumes or on the selected volume at the specified mount point.	Server Visibility					Advanced (volume)
Used (%)	The percentage of storage space in use across all listed volumes or on the selected volume at the specified mount point.	Server Visibility					KPI
Count	The number of partitions for which storage space metrics are collected.	Server Visibility					KPI
<partition> Free (MB)	The amount of unused or free space for <partition>.	Server Visibility					KPI
<partition> Total (MB)	The amount of storage space available (used and free) for <partition>.	Server Visibility					KPI
<partition> Used (%)	The percentage of storage space in use for <partition>.	Server Visibility					KPI
<partition> Used (MB)	The amount of storage space in use for <partition>.	Server Visibility					Advanced

¹Only /dev volumes are monitored on Linux.

²Only /dev/dsk and /rpool volumes are monitored on Solaris.

³See Default Monitoring Mode.

The load metrics are reported for each machine. The CPU % (reported as part of the basic Machine Agent metrics) is the percentage of the CPU consumed by processes that are currently running. Load takes into account processes that are waiting to run. These metrics are shown as percentages in the Server Dashboard and are scaled by 100 in the Metric Browser.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Last 1 minute	CPU Load, presented as an average over the last 1 minute.	Server Visibility					KPI
Last 5 minutes	CPU Load, presented as an average over the last 5 minutes.	Server Visibility					KPI
Last 15 minutes	CPU Load, presented as an average over the last 15 minutes.	Server Visibility					KPI

¹See Default Monitoring Mode.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Availability	The percentage of time the Machine Agent was reporting to the Controller. In the Server Visibility UI, this provides a percentage with 6 digits of precision (for example, 100.0000) to measure availability. The Machine Agent sends a heartbeat to the Splunk AppDynamics Controller once per minute to indicate the agent is reporting. Reported for each machine.	Server Visibility					KPI

¹See Default Monitoring Mode.

The Machine Agent is configured to ignore virtual networks by default. See Machine Agent Settings for Server Visibility.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Incoming KB2	The volume of data received by all monitored network devices.	Basic					Advanced
Incoming KB/sec	The amount of data per second received by all monitored network devices.	Basic					KPI
Incoming packets2	The number of packets received by all monitored network devices.	Basic					Advanced
Incoming packets/sec	The number of data packets per second received by all monitored network devices.	Basic					Advanced
Outgoing KB2	The volume of data sent by all monitored network devices.	Basic					Advanced
Outgoing KB/sec	The volume of data sent per second by all monitored network devices.	Basic					KPI
Outgoing packets2	The number of packets sent by all monitored network devices.	Basic					Advanced
Outgoing packets/sec	The number of data packets sent per second by all monitored network devices.	Basic					Advanced
Incoming Errors/min	The number of incoming packet errors the network incurs every minute.	Server Visibility					KPI
Outgoing Errors/min	The number of outgoing packet errors the network incurs every minute.	Server Visibility					KPI
Avg Utilization (%)	The average network utilization as a percentage of the maximum possible throughput. This metric is not reported if the agent cannot determine the throughput (not supported for some devices and Linux versions). The percentage is rounded to the nearest integer. Therefore, very low utilization may be reported as 0%. Reported for: Servers <group> <network interface>	Server Visibility					KPI
<network interface> Incoming KB	The volume of data received by the selected network interface.	Basic					Advanced
<network interface> Incoming KB/sec	The volume of data received per second by the selected network interface.	Basic					KPI
<network interface> Incoming packets	The number of data packets received by the selected network interface.	Basic					Advanced
<network interface> Incoming packets/sec	The number of data packets received per second by the selected network interface.	Basic					Advanced
<network interface> Outgoing KB	The volume of data sent by the selected network interface.	Basic					Advanced
<network interface> Outgoing KB/sec	The volume of data sent per second by all monitored network interface.	Basic					KPI
<network interface> Outgoing packets	The number of data packets sent per second by the selected network interface.	Basic					Advanced
<network interface> Outgoing packets/sec	The number of data packets sent per second by the selected network interface.	Basic					Advanced
<network interface>Incoming Errors/min	The number of incoming packet errors the network incurs every minute.	Server Visibility					KPI
<network interface>Outgoing Errors/min	The number of outgoing packet errors the network incurs every minute.	Server Visibility					KPI

¹See Default Monitoring Mode.

²The ServerMonitoring and JavaHardwareMonitor extensions calculate unidirectional throughput (packet/KB) metrics differently. ServerMonitoring reports the total number of packets/bytes in the last minute. JavaHardwareMonitor reports the total number of packets/bytes from the time the Machine Agent started.

The following metrics are aggregated and reported for each process or process class (except Total Process Count, which measures all processes observed by the agent). See Machine Agent Settings for Server Visibility to modify the default process monitoring.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Count	The number of processes in this class consuming CPU or memory resources or the total number of processes in this class.	Server Visibility					KPI
CPU Used (%)	Percentage of the CPU bandwidth used by all processes in a process class. A process using 100% CPU is executing on all processors on the system. If there are four cores on the machine and the process is executing four threads, each executing on one core, then the process can use up to 400% CPU. If there are four cores on the machine and the process is executing one thread on one core, then the process can use up to 25% CPU.	Server Visibility					KPI
Major Faults/sec	Number of major page faults caused by all processes in this class.	Server Visibility					Diagnostic
Minor Faults/sec	Number of minor page faults caused by all processes in this class.	Server Visibility					Diagnostic
Memory Used (%)	Percentage of memory consumed by the top 10 consuming processes or the percentage of memory used by all processes in this class.	Server Visibility					KPI
Memory Used (KB)	Amount of memory used by all processes in this class.	Server Visibility					Advanced
Memory Virtual (KB)	Current size of the virtual address space that the process is using. Use of virtual address space does not necessarily imply a corresponding use of either disk or main memory pages. Virtual space is finite and, by using too much, the process can limit its ability to load libraries.	Server Visibility					Advanced
Thread Count	The number of kernel threads used by all processes in this class.	Server Visibility					Diagnostic
Total Process Count	All individual processes observed by the Machine Agent,beforeit filters out unreported processes and groups the remaining processes into classes. You can use this metric to identify anomalies in the number of processes running on a specific machine. For example, if the average Total Process Count on a machine is usually 200 to 300, and then suddenly rises to 2000 or more, this could indicate a problem on that machine. To collect this metric, the Machine Agent captures the number of processes every 30 seconds and calculates the average number of processes per minute. Observed is the average number of processes per minute. Min and Max are the 30-second buckets with the least and most processes. Count and Sum are the number of process captures each minute and the sum of the processes in each capture for that minute (capture1 + capture2).	Server Visibility					KPI

¹See Linux Kernel Processes.

²When collecting Process metrics on Solaris, the Machine Agent observes and captures only the first 80 characters of each process name and argument list. The agent considers only the first 80 characters of each process string when it applies allowlists ("always monitor this process") and blocklists ("never monitor this process") defined inServerMonitoring.yml.

³See Default Monitoring Mode.

Reported for each service that is configured.

Metric Name	Description	Basic or Server Visibility	Windows	Linux	Solaris	AIX	Default Monitoring Mode
Response Time (ms)	The elapsed time between sending a request and receiving a response from the monitored service.	Server Visibility					KPI
Response Size (bytes)	The size of the response received from the monitored service.	Server Visibility					KPI
Success Rate (%)	The percentage of successful requests over all requests made to the service.	Server Visibility					KPI

¹See Default Monitoring Mode.

モニター対象の各URLについて、次のメトリックが集約および報告されます。ping コマンドを使用して、Web サイト（ URLで識別）がアクセス可能かどうかを定期的に確認するプロセス。Web サイトにデータパケットを送信して応答を受信するためにかかる時間を測定することで、基本的にその稼働時間とネットワーク接続をテストします。 。デフォルトのプロセスモニタリングを変更するには、 「サーバーの可視性のためのマシンエージェントの設定」を 参照してください。

メトリック名	説明	基本またはサーバの可視性	Windows	Linux：1	Solaris 2	AIX	デフォルトのモニタリングモード3
PING平均RTT (ミリ秒)	ping テストで測定されたラウンドトリップ時間（RTT）。これは、データパケットがデバイスから宛先サーバーに移動し、戻ってくるまでにかかる平均時間です。ミリ秒（ms）単位で表示されます。平均RTTが低いほど、接続が高速であることを意味します。	サーバーの可視性					KPI
PING最大RTT (ミリ秒)	記録された最大のRTTです。	サーバーの可視性	対応				KPI
PING MDEV（ミリ秒）	これは、ping コマンド出力の平均価格偏差です。ここには、平均RTTからのRTTの平均価格偏差が表示され、テスト中に応答時間がどのくらい変化したかを示します。	サーバーの可視性					KPI
PING最小RTT (ミリ秒)	これは、記録された最小のRTTです。	サーバーの可視性					KPI
受信パケット数（%）	送信されたパケットの総数のうち、目的の接続先に正常に到達したデータパケットの割合です。ネットワークがパケットを失うことなく、どの程度良好にデータを送信しているかを示します。パーセンテージが高いほど、ネットワーク パフォーマンスが向上し、パケット損失が減少することを意味します。	サーバーの可視性					KPI
ポートRTT (ミリ秒)	これは、データパケットがデバイスからサーバーの特定のポートに移動し、戻ってくるまでにかかる時間を示します。その特定のポート接続の遅延を測定します。	サーバーの可視性					KPI

You must enable percentile metric reporting on both the Controller and the Machine Agent. By default, reporting isdisabledon the Controller andenabledon the Machine Agent.

• To enable/disable reporting on the Controller, log in to the Controller Administration Console and set the sim.machines.percentile.percentileMonitoringAllowed property. See Controller Settings for Machine Agents.
• To enable/disable reporting on the agent, open the <machine_agent_home>/extensions/ServerMonitoring/conf/ServerMonitoring.yml file and set the percentileEnabled property. See Machine Agent Settings for Server Visibility.

You can configure the Linux Machine Agent to calculate the following metrics similar to using the Linux df

• Servers > Volumes > /opt > Disk Usage
• Metric Browser > Disks and Partitions > <partition> > Space Available
• Metric Browser > Disks and Partitions > <partition> > Space Used

Linux includes a mechanism for reserving some disk space to ensure that the system remains functioning even if non-privileged users consume all other disk space. By default, these metrics include 5% of reserved space.

By default, the flag -Dappdynamics.machine.agent.extensions.calcVolumeFreeAndUsedWithDfCommand true

To override this default, set -Dappdynamics.machine.agent.extensions.calcVolumeFreeAndUsedWithDfCommand false

This feature is supported for Linux versions of the Machine Agent only.

You can configure how the Machine Agent calculates the amount of free and used memory on Linux machines. By default, the agent calculates any slab-reclaimable memory as used (not free) memory. To configure the agent to calculate slab-reclaimable memory as free (not used) memory, run Machine Agent with the following command-line argument:

-Dappdynamics.machine.agent.extensions.countSlabReclaimableAsFreeMem=true

• Memory Usage (in Server Dashboard)
• Memory Used %, Memory Used MB, Memory Free %, and Memory Free MB (in Metric Browser)

You can use the following system property to exclude the file cache memory while calculating memory usage on AIX with server visibility enabled.

If you set < -Dappdynamics.machine.agent.collect.memoryMetrics.using.vmstat.command = true> sim_enabled = true>

You can use the following two system properties to configure how the operating system and hardware information (OSHI) data is collected and sent to Controller.

Example 1:

-Dappdynamics.machine.agent.oshiCollectionTimeout.in.ms=1000
-Dappdynamics.machine.agent.should.drop.complete.process.data.when.timeout=false

In this case, if the OSHI data collection process takes more than 10000 milliseconds, then the agent sends the OSHI data collected within 10000 milliseconds.

Example 2:

-Dappdynamics.machine.agent.oshiCollectionTimeout.in.ms=1000
-Dappdynamics.machine.agent.should.drop.complete.process.data.when.timeout=true

In this case, if the OSHI data collection process takes more than 10000 milliseconds, then the agent does not send any data to Collector.

サーバの可視性メトリックは、メトリックブラウザのサーバの可視性バージョンでのみ表示できます。これは、コントローラ UI の上部のナビゲーションバーにある [Servers] タブからメトリックブラウザにアクセスすると表示されます。

マシンエージェントと .NET マシンエージェント

サーバーにマシンエージェントと .NET エージェントの両方がインストールされている場合、平均化レートや測定方法の違いにより、マシンエージェントと .NET エージェントが報告するメトリック値に差異が生じることがあります。.NET 互換モード.NET 互換モード

効率的なブラウジングモード

サーバメトリックブラウザには、ノードメトリックのために効率的なブラウジングのオプションが含まれます。このオプションは、複数のノードを含む階層のメトリックをブラウズする場合に使用します。

• 効率的なブラウジングが有効になっている場合、ブラウザツリービューの各ノードには、対応するノードのマシンエージェントによってレポートされたメトリックのみが表示されます。
• 効率的なブラウジングが有効になっている場合、Hardware Resources および Custom Metrics フォルダは表示されません。
• 効率的なブラウジングが無効になっている場合、ブラウザツリービューの各ノードには、同じ階層内の他のノードのメトリックも表示されます（どの階層グループに対応するノードであるかは示されません）。

この効率化オプションは、デフォルトで無効になっています。Splunk AppDynamics では、このオプションを有効にすることを推奨しています。このオプションを有効にするには、以下に移動します。

http://<controller host>:<port>/controller/admin.jsp and set sim.metrics.metricBrowser.machineMetricMappings.enabled to true.

Linux カーネルプロセス

マシンエージェントには、エージェントがモニターする一連のプロセスを指定する正規表現の processSelectorRegex 設定があります。デフォルトの

デフォルトのモニタリングモード

[Default Monitoring Mode] 列は、動的モニタリングモード（DMM）が有効になっている場合に各メトリックのデフォルトカテゴリを示します。このモードが有効になっている場合、マシンエージェントはそのサーバーの DMM 設定に基づいてメトリックをレポートします。

• KPI：重要業績評価指標のみレポートします。
• Diagnostic：KPI と診断メトリックをレポートします。
• Advanced：マシンエージェントのフィルタ処理されていないすべてのメトリックをレポートします。

メトリックブラウザでは負荷平均のパーセンテージに 100 が乗算される

負荷平均のメトリックは、サーバーダッシュボードで float 値（0.70 や 1.05 など）として表示されます。メトリックブラウザでは、これらのメトリックは 100 で乗算され、小数点が 2 つ移動します。たとえば、サーバの平均負荷が 7.67 の場合、サーバダッシュボードには、負荷平均は 7.67 と表示され、メトリックブラウザには 767 と表示されます。正常性ルールまたはカスタムダッシュボードでいずれかのメトリックを使用する場合は、メトリックを 100 で除算します。

盗難時間が異なる方法でレポートされる

Windows マシンエージェントで、CPU %Stolen が Splunk AppDynamics によってレポートされた値と一致しない場合、Windows Performance Monitor（Perfmon）のカウンタが CPU メトリックに対して 100 ナノ秒単位で動作することが原因である可能性があります。CPU %Stolen では、カウンタはハイパーバイザによって提供されます。これは、1 ミリ秒単位で動作します。Windows Perfmon では、CPU %Stolen カウンタ（1 ミリ秒単位で動作）が時間（100 ナノ秒単位）で直接除算されます。これにより、CPU %Stolen 値が非常に低いパーセンテージ（～ 0.01%）でレポートされます。

Splunk AppDynamics は、異なる時間単位の間で修正を行います。これは、Splunk AppDynamics によってレポートされる値が、10,000 の係数（1 ミリ秒単位の時間 * 10,000 = 100 ナノ秒単位の時間）によって Perfmon の値よりも大きくなるためです。Splunk AppDynamics によってレポートされる CPU %Stolen 値は、負荷が高い状況では 100% を超えることがあります。これらの CPU %Stolen 値は、ゲストマシンによって複数のコアが使用された結果であり、ここで、%Stolen 時間が複数のコア間で追加されます。

%Stolen 時間を計算するには、次のようにします。

1. モニター対象のゲストマシンの PowerShell 端末で、Get-WmiObject Win32_PerfRawData_vmGuestLib_VCPU. を実行します。
2. CpuStolenMs カウンタ（ミリ秒単位）をメモします。
3. Timestamp_PerfTime カウンタ（ミリ秒単位）をメモします（Frequency_Perftime を確認します。この値は 1000（hz 単位）になっているはずです）。
4. 1 分後に Get-WmiObject Win32_PerfRawData_vmGuestLib_VCPU をもう一度実行し、両方のカウンタを再度メモします。
5. CPU %Stolen = 100% * (CpuStolenMS (at T2) - CpuStolenMs (at T1) / (Timestamp_PerfTime (T2) - Timestamp_PerfTime (T1))。

AIX マシンで HardwareMonitor と JavaHardwareMonitor により「書き込み/秒」が異なる方法で計算される

マシンエージェントは、HardwareMonitor 拡張機能と JavaHardwareMonitor 拡張機能のどちらが使用されているかに基づき、AIX マシンでディスクメトリックの書き込み/秒を異なる方法で計算します。これらの拡張機能は、これらのメトリックを計算するときに異なるブロックサイズを想定しています。HardwareMonitor では、ブロックサイズは 4096 バイトです。（SIGAR に基づく）JavaHardwareMonitor では、ブロックサイズは 512 バイトです。書き込み数/秒は、<kb_written>/<block_size> として計算されるため、HardwareMonitor の結果は、JavaHardwareMonitor によって計算される結果よりも少なくなります。