| 2015-07-31 20:46:32 |
gordon chung |
description |
with a pipeline
sources:
- name: meter_source
interval: 5
meters:
- "*"
sinks:
- meter_sink
sinks:
- name: meter_sink
transformers:
publishers:
- udp://
everything will be polled once. makes sense.
with a pipeline:
sources:
- name: meter_source
interval: 5
meters:
- "*"
sinks:
- meter_sink
- name: meter2_source
interval: 5
meters:
- "*"
sinks:
- meter_sink
sinks:
- name: meter_sink
transformers:
publishers:
- udp://
everything is polled twice. makes no sense. |
with a pipeline
sources:
- name: meter_source
interval: 5
meters:
- "*"
sinks:
- meter_sink
sinks:
- name: meter_sink
transformers:
publishers:
- udp://
everything will be polled once. makes sense.
with a pipeline:
***updated (31/07/15)***
sources:
- name: meter_source
interval: 600
meters:
- "*"
sinks:
- meter_sink
- name: cpu_source
interval: 600
meters:
- "cpu"
sinks:
- cpu_sink
sinks:
- name: meter_sink
transformers:
publishers:
- notifier://
- name: cpu_sink
transformers:
- name: "rate_of_change"
parameters:
target:
name: "cpu_util"
unit: "%"
type: "gauge"
scale: "100.0 / (10**9 * (resource_metadata.cpu_number or 1))"
publishers:
- notifier://
cpu is polled twice. this isn't needed. |
|
