a0f873f413
Adding capabilities to ceilosca to be able to query metrics that are already being collected by monasca using mappings files there are two types of mappings: 1. Static Mapping: Currently it is used to map any static info about ceilometer meters like the type of meter or unit 2. Extensive monasca mapping: currently it is used to map any monasca metric to a ceilometer meter example: meter_metric_map: - name: "disk.device.write.requests" monasca_metric_name: "vm.io.write_ops" resource_id: $.dimensions.resource_id project_id: $.dimensions.tenant_id user_id: $.dimensions.user_id region: "NA" type: "cumulative" unit: "request" source: "NA" resource_metadata: $.measurement[0][2] As you can see for this mapping fields on left side of ":" are used to map ceilometer fields and fields on right side for referring to monasca fields Both of these mapping files are configurable and can be set in ceilometer configuration file cloud_name, cluster_name, and control plane fields are now added as dimensions by monasca publisher when publishing metrics to monasca api which is necessary in multi-region deployment of notification agent. monasca publisher does not use oslo.service LoopingCall but instead uses futurist periodics library to enable batching. monasca client now pages through monasca api results if enable_api_pagination is enabled in configuration. This flag is disabled by default but should be enabled if monasca api supports paging using "offsets" parameter. Tox testing is now targeting stable/newton branch of ceilometer. DocImpact Change-Id: I83b96325cb79d82858cf529935e5d699a509f6c3
14 lines
250 B
YAML
14 lines
250 B
YAML
---
|
|
sources:
|
|
- name: meter_source
|
|
interval: 60
|
|
meters:
|
|
- "instance"
|
|
sinks:
|
|
- meter_sink
|
|
sinks:
|
|
- name: meter_sink
|
|
transformers:
|
|
publishers:
|
|
- monasca://http://192.168.10.6:8070/v2.0
|