The Orchestrate Agent uses the metrics collected by gmond to create fact values for a given resource. These facts are therefore externally generated and are not among the default facts reported by the PlateSpin Orchestrate Agent. The agent updates these externally generated fact values every 30 seconds. All of these fact values have a resource.metrics. prefix.
For example, gmond collects a metrics value called load_one. The Orchestrate Agent sets this value as the resource.metrics.load_one fact.
To see a list of these facts in the Orchestrate Development Client,
In the Explorer panel, select a resource.
In the Workspace panel, select .
The names of the resource metrics facts are displayed in bold font because they were added as new facts to the default fact list. The following sample is a list of the default Ganglia-generated metrics facts with data type and an example value:
<fact name="resource.metrics.boottime" value="1239122234.0000" type="Real" /> <fact name="resource.metrics.bytes_in" value="208.8800" type="Real" /> <fact name="resource.metrics.bytes_out" value="68.9700" type="Real" /> <fact name="resource.metrics.cpu_aidle" value="76.9000" type="Real" /> <fact name="resource.metrics.cpu_idle" value="95.2000" type="Real" /> <fact name="resource.metrics.cpu_nice" value="0.0000" type="Real" /> <fact name="resource.metrics.cpu_num" value="2" type="Integer" /> <fact name="resource.metrics.cpu_speed" value="1596" type="Integer" /> <fact name="resource.metrics.cpu_system" value="0.3000" type="Real" /> <fact name="resource.metrics.cpu_user" value="4.0000" type="Real" /> <fact name="resource.metrics.cpu_wio" value="0.4000" type="Real" /> <fact name="resource.metrics.disk_free" value="27090" type="Integer" /> <fact name="resource.metrics.disk_total" value="48213" type="Integer" /> <fact name="resource.metrics.gexec" value="OFF" type="String" /> <fact name="resource.metrics.load_fifteen" value="0.2000" type="Real" /> <fact name="resource.metrics.load_five" value="0.4100" type="Real" /> <fact name="resource.metrics.load_one" value="1.1900" type="Real" /> <fact name="resource.metrics.machine_type" value="x86" type="String" /> <fact name="resource.metrics.mem_buffers" value="299" type="Integer" /> <fact name="resource.metrics.mem_cached" value="761" type="Integer" /> <fact name="resource.metrics.mem_free" value="65" type="Integer" /> <fact name="resource.metrics.mem_shared" value="0" type="Integer" /> <fact name="resource.metrics.mem_total" value="1989" type="Integer" /> <fact name="resource.metrics.os_name" value="Linux" type="String" /> <fact name="resource.metrics.os_release" value="2.6.27.19-5-pae" type="String" /> <fact name="resource.metrics.part_max_used" value="70.8000" type="Real" /> <fact name="resource.metrics.part_max_used.units" value="" type="String" /> <fact name="resource.metrics.pkts_in" value="0.4500" type="Real" /> <fact name="resource.metrics.pkts_out" value="0.6300" type="Real" /> <fact name="resource.metrics.proc_run" value="0" type="Integer" /> <fact name="resource.metrics.proc_total" value="411" type="Integer" /> <fact name="resource.metrics.swap_free" value="2039" type="Integer" /> <fact name="resource.metrics.swap_total" value="2047" type="Integer" /> <fact name="resource.metrics.vm_type" value="" type="String" /> <fact name="resource.metrics.vm_type.units" value="" type="String" />
These are the metrics reported in Orchestrate systems that use the gmond.conf created when Orchestrate Monitoring Agent was installed and configured. The open source gmond might include other metrics that can be monitored. You can modify the default Orchestrate gmond configuration file to report these metrics after it is initially installed and configured. For information about modifying the file, see the gmond.conf man page.
By using the XML constraint language, you can utilize these resource metrics facts as you would use any other fact in PlateSpin Orchestrate. For example, you could create an Event that sets thresholds for the amount of incoming network packets. When that threshold is exceeded, a Scheduled Job could be triggered or a notification e-mail sent. For more information, see Section 7.14, Using an Event Notification in a Job.