Follow

Overview

InfiniMetrics provides an API for getting the raw data that is collected for each monitored entity. The complete list of monitored entities can be acquired using this API endpoint: /api/rest/systems/<system-serial>/monitored_entities/ . The data collected for a specific monitored entity is available via /api/rest/systems/<system-serial>/monitored_entities/<entity-id>/data/ . Each type of monitored entity (e.g. host, volume, filesystem) has a different set of data fields, as specified in the following sections.

NAS

NAS Totals, Filesystems, Pools

These entities have the following data fields:

  • timestamp - UTC date and time, for example "2018-05-18T00:31:02Z"
  • <type>_ops - number of I/O operations per second of the given type. The type is one of read, write, metadata.
  • <type>_bytes - throughput in bytes per second of the given type. The type is one of read, write, metadata.
  • <type>_latency - average operation latency (in milliseconds) of the given type. The type is one of read, write, metadata.
  • ram_cache_hit_ratio - the ratio of read operations that were served from the RAM cache (between 0 and 1)
  • ssd_cache_hit_ratio - the ratio of read operations that were served from the SSD cache (between 0 and 1)

IO By Size

IO By Size data includes read and write statistics separated into "buckets" according to the operation's block size.

  • timestamp - UTC date and time, for example "2018-05-18T00:31:02Z"
  • read_ops_<bucket> - number of I/O operations per second for read operations in the bucket's block size range.
  • read_bytes_<bucket> - throughput in bytes per second for read operations in the bucket's block size range.
  • read_latency_<bucket> - throughput in bytes per second for read operations in the bucket's block size range.
  • write_ops_<bucket> - number of I/O operations per second for write operations in the bucket's block size range.
  • write_bytes_<bucket> - throughput in bytes per second for write operations in the bucket's block size range.
  • write_latency_<bucket> - throughput in bytes per second for write operations in the bucket's block size range.

The block size ranges (buckets) are:

  • lt_512b - less than 512 bytes
  • ge_512b_lt_1k - 512 bytes to under 1KiB
  • ge_1k_lt_2k - 1KiB to under 2KiB
  • ge_2k_lt_4k - 2KiB to under 4KiB
  • ge_4k_lt_8k - 4KiB to under 8KiB
  • ge_8k_lt_16k - 8KiB to under 16KiB
  • ge_16k_lt_32k - 16KiB to under 32KiB
  • ge_32k_lt_64k - 32KiB to under 64KiB
  • ge_64k_lt_128k - 64KiB to under 128KiB
  • ge_128k - 128KiB and larger

SAN

Hosts, Clusters

These entities have the following data fields:

  • timestamp - UTC date and time, for example "2018-05-18T00:31:02Z"
  • <type>_ops - number of I/O operations per second of the given type. The type is one of read, write, writesame, xcopy.
  • <type>_bytes - throughput in bytes per second of the given type. The type is one of read, write, writesame, xcopy.
  • <type>_latency - average operation latency (in milliseconds) of the given type. The type is one of read, write, writesame, xcopy.
  • ram_cache_hit_ratio - the ratio of read operations that were served from the RAM cache (between 0 and 1)
  • ssd_cache_hit_ratio - the ratio of read operations that were served from the SSD cache (between 0 and 1)

SAN Totals

The SAN system totals includes all fields that hosts have, with the addition of the unmap operation type. Meaning it has 3 additional fields: unmap_ops, unmap_bytes and unmap_latency.

Volumes, Pools

Volumes and pools include all fields that hosts have, with the addtion of:

  • max_ops - the maximum number of operations per second according to this entity's QoS policy, or null if no policy is assigned.
  • max_bps - the maximum number of bytes per second according to this entity's QoS policy, or null if no policy is assigned.

IO By Size

IO By Size data includes read and write statistics separated into "buckets" according to the operation's block size.

  • timestamp - UTC date and time, for example "2018-05-18T00:31:02Z"
  • read_ops_<bucket> - number of I/O operations per second for read operations in the bucket's block size range.
  • read_bytes_<bucket> - throughput in bytes per second for read operations in the bucket's block size range.
  • read_latency_<bucket> - throughput in bytes per second for read operations in the bucket's block size range.
  • write_ops_<bucket> - number of I/O operations per second for write operations in the bucket's block size range.
  • write_bytes_<bucket> - throughput in bytes per second for write operations in the bucket's block size range.
  • write_latency_<bucket> - throughput in bytes per second for write operations in the bucket's block size range.

The block size ranges (buckets) are:

  • lt_4k - less than 4KiB
  • ge_4k_lt_8k - 4KiB to under 8KiB
  • ge_8k_lt_32k - 8KiB to under 32KiB
  • ge_32k_lt_64k - 32KiB to under 64KiB
  • ge_64k_lt_512k - 64KiB to under 512KiB
  • ge_512k - 512KiB and larger

Other

Pool Capacity

Pool capacity entities have the following data fields:

  • timestamp - UTC date and time, for example "2018-05-18T00:31:02Z"
  • physical_capacity - the pool's physical capacity in bytes
  • virtual_capacity - the pool's virtual capacity in bytes
  • free_physical_space - the amount of free physical space in bytes
  • free_virtual_space - the amount of free virtual space in bytes
  • allocated_physical_space - the amount of allocated physical space in bytes
  • allocated_virtual_space - the amount of allocated virtual space in bytes
  • filesystems_count - number of filesystems in the pool
  • snapshots_count - number of volume snapshots in the pool
  • volumes_count - number of volumes in the pool
  • filesystem_snapshots_count - number of filesystem snapshots in the pool
  • clones_count - obsolete




Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Comments