Jump to: navigation, search

Difference between revisions of "Ceilometer/blueprints/transportation-pipeline-monitoring-metrics"

(Created page with "== Summary == Compared to metering data, the monitoring metrics need to be collected in a more frequent fashion and the amount of data is way bigger. Does the monitoring metri...")
 
(Alternative for metrics pipeline)
Line 30: Line 30:
  
 
<gallery>
 
<gallery>
File:ceilometer-metrics-pipeline-proposal.jpg|Alternative for metrics pipeline
+
[[Image:ceilometer-metrics-pipeline.jpg]]
</gallery>
 

Revision as of 09:15, 7 April 2013

Summary

Compared to metering data, the monitoring metrics need to be collected in a more frequent fashion and the amount of data is way bigger. Does the monitoring metrics necessarily need to go through the message bus as metering data does. Or the option worth being considered is to write them directly to data store.

The current metering pipeline

---
-
    name: meter_pipeline
    interval: 60
    counters:
        - "*"
    transformers:
    publishers:
        - meter_publisher

Alternative for metrics pipeline

---
-
    name: metrics_pipeline
    interval: 5   // more frequent polling might be needed by monitoring
    counters:
        - "*"
    transformers:
    publishers:
        - metrics_publisher     // metrics publisher might directly write to backend storage (avoid MQ)
        - metrics_notifier(publisher)     // inline pre-processing metrics notification

<gallery> File:Ceilometer-metrics-pipeline.jpg