|Zuul 73cf293aec Merge "Dropping the py35 testing"||1 week ago|
|devstack||3 weeks ago|
|doc/source||1 year ago|
|docs||10 months ago|
|etc||1 year ago|
|monasca_transform||1 month ago|
|scripts||2 years ago|
|tests||1 month ago|
|tools/vagrant||3 weeks ago|
|.gitignore||10 months ago|
|.gitreview||1 month ago|
|.stestr.conf||10 months ago|
|.zuul.yaml||1 month ago|
|LICENSE||3 years ago|
|README.rst||8 months ago|
|lower-constraints.txt||10 months ago|
|requirements.txt||1 year ago|
|setup.cfg||5 months ago|
|setup.py||2 years ago|
|test-requirements.txt||10 months ago|
|tox.ini||1 week ago|
monasca-transform is a data driven aggregation engine which collects, groups and aggregates existing individual Monasca metrics according to business requirements and publishes new transformed (derived) metrics to the Monasca Kafka queue.
Please refer to Problem Description section on the Monasca/Transform wiki
Please refer to How Monasca Transform Operates section on the Monasca/Transform wiki
Please refer to Architecture and Logical processing data flow sections on the Monasca/Transform wiki
Monasca Transform uses a set of generic aggregation components which can be assembled in to an aggregation pipeline.
Please refer to the generic-aggregation-components document for information on list of generic aggregation components available.
Generic aggregation components make it easy to build new aggregation pipelines for different Monasca metrics.
This create a new aggregation pipeline example shows how to create pre_transform_specs and transform_specs to create an aggregation pipeline for a new set of Monasca metrics, while leveraging existing set of generic aggregation components.
Original proposal: Monasca/Transform-proposal
Blueprint: monasca-transform blueprint