---
sources:
    - name: meter_source
      interval: 600
      meters:
          - "*"
      sinks:
          - meter_sink
    - name: disk_source
      interval: 600
      meters:
          - "disk.read.bytes"
          - "disk.read.requests"
          - "disk.write.bytes"
          - "disk.write.requests"
          - "disk.device.read.bytes"
          - "disk.device.read.requests"
          - "disk.device.write.bytes"
          - "disk.device.write.requests"
      sinks:
          - disk_sink
sinks:
    - name: meter_sink
      transformers:
      publishers:
          - notifier://
    - name: disk_sink
      transformers:
          - name: "rate_of_change"
            parameters:
                source:
                    map_from:
                        name: "(disk\\.device|disk)\\.(read|write)\\.(bytes|requests)"
                        unit: "(B|request)"
                target:
                    map_to:
                        name: "\\1.\\2.\\3.rate"
                        unit: "\\1/s"
                    type: "gauge"
      publishers:
          - notifier://

Remove cpu_sink as it does not pertain to powervm
Remove cpu_sink as it does not pertain to powervm

The cpu_sink as defined in the default pipeline.yaml does not apply to
PowerVM.  This is because the PowerVM compute inspector has a CPU
Utilization inspector built in.

This change provides an updated default pipeline.yaml that is applicable
for operators wishing to make use of the powervm compute inspector.

This change also removes the network sink as that was also an issue as
network metrics came back.

Change-Id: I4e7cae715fc77c5e399bd3c6d33afdc8fa02d890
Closes-Bug: 1475362
