Jump to: navigation, search

Difference between revisions of "Ceilometer/blueprints/monitoring-metrics-object"

(Meters)
(Meters)
Line 1: Line 1:
 
== Meters ==
 
== Meters ==
 
In Ceilometer, the meters are polled in the form of Counter(namedtuple) as below, do we need two different peer objects or a common lower level object for both meters and metrics?
 
In Ceilometer, the meters are polled in the form of Counter(namedtuple) as below, do we need two different peer objects or a common lower level object for both meters and metrics?
:Counter = collections.namedtuple('Counter',
+
<pre>
:                                ' '.join([
+
Counter = collections.namedtuple('Counter',
:                                    'name',
+
                                ' '.join([
:                                    'type',
+
                                    'name',
:                                    'unit',
+
                                    'type',
:                                    'volume',
+
                                    'unit',
:                                    'user_id',
+
                                    'volume',
:                                    'project_id',
+
                                    'user_id',
:                                    'resource_id',
+
                                    'project_id',
:                                    'timestamp',
+
                                    'resource_id',
:                                    'resource_metadata',
+
                                    'timestamp',
:                                ]))
+
                                    'resource_metadata',
 +
                                ]))
 +
</pre>
  
 
== Monitoring Metrics ==
 
== Monitoring Metrics ==

Revision as of 08:56, 7 April 2013

Meters

In Ceilometer, the meters are polled in the form of Counter(namedtuple) as below, do we need two different peer objects or a common lower level object for both meters and metrics?

Counter = collections.namedtuple('Counter',
                                 ' '.join([
                                     'name',
                                     'type',
                                     'unit',
                                     'volume',
                                     'user_id',
                                     'project_id',
                                     'resource_id',
                                     'timestamp',
                                     'resource_metadata',
                                 ]))

Monitoring Metrics

As the monitoring metrics, take ganglia metric as an example(Gmetad XML dump):

-Host
-Cluster Name
-METRIC NAME="swap_free"
-VAL="2097148"
-TYPE="float"
-UNITS="KB"
-TN="138" - timestamp
-TMAX="180" (like a leasetime - freshness)
-DMAX="0" (how long to retain old records)
-SLOPE="both" (+ = counter, others = gauge)

Mapping

Ceilometer Counter Ganglia Metric
name METRICNAME
delta|cumulative) positive|negative|both) more from metadata
unit UNITS
volume VAL
user_id None (appropriate for a meter, not monitor)
project_id None (appropriate for a meter, not monitor)
resource_id(swift: tenant_id, compute:instance_id, glance:image_id) Host (FQDN)
timestamp Ganglia TN (current time - TN = timestamp when metric published)
resource_metadata NONE