#Diamond

Diamond Agent

Diamond’s default HTTP Post Handler can be used to send Diamond data to Metricly. Configuration 1. Copy the unique API key from the Diamond integration in your account In Metricly, navigate to Integrations. Click the Diamond card. Data collection should already be enabled, and a unique API key for your account has already been generated. Copy the API key. 2. Install & Configure Diamond Download and install Diamond using the instructions found here.

Diamond Agent Metrics

All of the metrics for the Diamond Agent can be found in this folder. Metrics Available Diamond CPU Metrics Diamond Disk Usage Metrics Diamond Diskspace Metrics Diamond Load Average Metrics Diamond Memory Metrics Diamond Network Metrics

Diamond CPU Metrics

Collected Fully Qualified Name(FQN) Description Statistic Units Min Max Sparse Data Strategy (SDS) BASE CORR UTIL cpu.total.guest Percentage of CPU spent running virtual CPUs for guest operatingsystems. average percent 0 none none yes no no cpu.total.guest_nice Percentage of CPU spent running low-priority virtual CPUs for guestoperating systems. average percent 0 none none yes no no cpu.total.idle Percentage of CPU not doing any work.

Diamond Disk Usage Metrics

Computed Fully Qualified Name(FQN) Description Units Min Max BASE CORR UTIL metriclyicly.linux.iostat.totalreads Total reads across all disks. Computation: data.sum(‘iostat\..*\.reads) 0 none yes no no metriclyicly.linux.iostat.totalwrites Total writes across all disks. Computation: data.sum(‘iostat\..*\.writes) 0 none yes no no

Diamond Diskspace Metrics

Collected Fully Qualified Name(FQN) Description Statistic Units Min Max Sparse Data Strategy (SDS) BASE CORR UTIL diskspace..byte_percentfree Percentage of free bytes. average percent 0 100 none yes no no Computed Fully Qualified Name(FQN) Description Units Min Max BASE CORR UTIL metriclyicly.linux.diskspace.*.byte_percentused Percentage of disk space used. Computation: 100 – diskspace.*.byte_percentfree percent 0 100 no no yes

Diamond Load Average Metrics

Computed Fully Qualified Name(FQN) Description Units Min Max BASE CORR UTIL metriclyicly.linux.loadavg.01.normalized The is the average run queue size over the past minute, normalizedacross CPUs. Computation: attribute[‘cpus’] == null ? null : (data[‘loadavg.01’].actual /attribute[‘cpus’].value) 0 none yes no no metriclyicly.linux.loadavg.05.normalized The is the average run queue size over the past 5 minutes, normalizedacross CPUs. Computation: attribute[‘cpus’] == null ? null : (data[‘loadavg.

Diamond Memory Metrics

Computed Fully Qualified Name(FQN) Description Units Min Max BASE CORR UTIL metriclyicly.linux.memory.utilizationpercent Under Linux, memory buffered and cached are part of memory which can beconsidered available. See the following explanation . Computation: 100 – (memory.Buffers + memory.Cached + memory.MemFree) /memory.MemTotal * 100 percent 0 100 yes yes yes

Diamond Network Metrics

Computed Fully Qualified Name(FQN) Description Units Min Max BASE CORR UTIL metriclyicly.linux.network.*.errors The total number of errors, both transmit and receive. Computation: network..rx_errors + network..tx_errors errors 0 none yes no no metriclyicly.linux.network.*.packets The total number of packets, both transmitted and received. Computation: network..rx_packets + network..tx_packets packets 0 none yes yes no metriclyicly.linux.network.*.errors.percent The percentage of errors, both transmit and receive.

Linux Policies

Before reading about these default policies, note that both the Elevated User CPU and Elevated System CPU policies assume that the CPU Collector is configured to collect aggregate CPU metrics, rather than per core metrics. It also assumes that the metrics are being normalized. This is done by setting the percore setting set to FALSE (it is TRUE by default) and the normalize setting set to TRUE (it is FALSE by default) in your configuration file.