i think this is a side effect of removing pipeline from polling agent -- the pipeline functionality doesn't actually apply anymore. if i put this in context of current pipeline:
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://
this will poll cpu twice. i don't need to poll twice. i just want the cpu meter and i want the cpu_util value i can derive from it.
i think this is a side effect of removing pipeline from polling agent -- the pipeline functionality doesn't actually apply anymore. if i put this in context of current pipeline:
sources:
parameters :
target:
name: "cpu_util"
unit: "%"
type: "gauge"
scale: "100.0 / (10**9 * (resource_ metadata. cpu_number or 1))"
- 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"
publishers:
- notifier://
this will poll cpu twice. i don't need to poll twice. i just want the cpu meter and i want the cpu_util value i can derive from it.