To verify this: * spin up instances with volumes via cli or dashboard * the metrics of interest are : - disk.device.read.bytes.rate" - "disk.device.read.requests.rate" - "disk.device.write.bytes.rate" - "disk.device.write.requests.rate" These are already part of the pipeline.yaml and derived through transformers. So these are essentially derived metrics. So just make sure these meters show up via cli. Let me know if you have any questions
Output from 'ceilometer sample-list' call +------------------------------------------+---------------------------------+-------+-----------------+-----------+---------------------+ | Resource ID | Name | Type | Volume | Unit | Timestamp | +------------------------------------------+---------------------------------+-------+-----------------+-----------+---------------------+ | 5a028ada-3c36-401d-82af-5744acbefd07-vdc | disk.device.write.requests.rate | gauge | 0.0169491525424 | request/s | 2015-04-22T09:44:03 | +------------------------------------------+---------------------------------+-------+-----------------+-----------+---------------------+ +------------------------------------------+------------------------------+-------+---------------+------+---------------------+ | Resource ID | Name | Type | Volume | Unit | Timestamp | +------------------------------------------+------------------------------+-------+---------------+------+---------------------+ | 5a028ada-3c36-401d-82af-5744acbefd07-vdc | disk.device.write.bytes.rate | gauge | 69.4237288136 | B/s | 2015-04-22T09:44:03 | +------------------------------------------+------------------------------+-------+---------------+------+---------------------+ +------------------------------------------+--------------------------------+-------+-----------------+-----------+---------------------+ | Resource ID | Name | Type | Volume | Unit | Timestamp | +------------------------------------------+--------------------------------+-------+-----------------+-----------+---------------------+ | 5a028ada-3c36-401d-82af-5744acbefd07-vdc | disk.device.read.requests.rate | gauge | 0.220338983051 | request/s | 2015-04-22T09:44:03 | +------------------------------------------+--------------------------------+-------+-----------------+-----------+---------------------+ +------------------------------------------+-----------------------------+-------+---------------+------+---------------------+ | Resource ID | Name | Type | Volume | Unit | Timestamp | +------------------------------------------+-----------------------------+-------+---------------+------+---------------------+ | 5a028ada-3c36-401d-82af-5744acbefd07-vdc | disk.device.read.bytes.rate | gauge | 93305.4915254 | B/s | 2015-04-22T09:44:03 | +------------------------------------------+-----------------------------+-------+---------------+------+---------------------+
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0930.html