Difference between revisions of "Ceilometer/blueprints/graphite-publisher"
< Ceilometer | blueprints
Shashi Dahal (talk | contribs) (ceilometer graphite plugin) |
Shashi Dahal (talk | contribs) |
||
Line 1: | Line 1: | ||
− | '''Context''' | + | == '''Context''' == |
We want to monitor resource usage for all the VMS group by tenants. We do not want to write our own plugin for monitoring, but use ceilometer. | We want to monitor resource usage for all the VMS group by tenants. We do not want to write our own plugin for monitoring, but use ceilometer. | ||
− | '''Problem''' | + | == '''Problem''' == |
Performance issues on saving records to sql and on query. | Performance issues on saving records to sql and on query. | ||
− | '''Solution''' | + | == '''Solution''' == |
− | To create a graphite publisher, so that ceilometer-compute agent can directly send the metrics to graphite. | + | To create a new graphite publisher, so that ceilometer-compute agent can directly send the metrics to graphite. |
Working Sample. | Working Sample. | ||
Line 12: | Line 12: | ||
ceilometer.project_id.resource_id.metric | ceilometer.project_id.resource_id.metric | ||
− | [[File: | + | [[File:Ceilometer graphite publisher.png|framed|Ceilometer Graphite Publisher]] |
Revision as of 11:18, 1 April 2014
Context
We want to monitor resource usage for all the VMS group by tenants. We do not want to write our own plugin for monitoring, but use ceilometer.
Problem
Performance issues on saving records to sql and on query.
Solution
To create a new graphite publisher, so that ceilometer-compute agent can directly send the metrics to graphite.
Working Sample. The metrics are send to graphite as: ceilometer.project_id.resource_id.metric