Bases: exceptions.Exception
Bases: object
Base class for managing configuration file refresh
Bases: ceilometer.pipeline.Pipeline
Represents a pipeline for Events.
Bases: ceilometer.pipeline._PipelineTransportManager
Bases: ceilometer.pipeline.Sink
Bases: ceilometer.pipeline.PipelineSource
Represents a source of events.
In effect it is a set of notification handlers capturing events for a set of matching notifications.
Bases: object
Represents a coupling between a sink and a corresponding source.
Bases: ceilometer.pipeline.ConfigManagerBase
Pipeline Manager
Pipeline manager sets up pipelines according to config file
Bases: ceilometer.pipeline.Source
Represents a source of samples or events.
Bases: ceilometer.pipeline.ConfigManagerBase
Polling Manager
Polling manager sets up polling according to config file.
Bases: ceilometer.pipeline.Source
Represents a source of pollsters
In effect it is a set of pollsters emitting samples for a set of matching meters. Each source encapsulates meter name matching, polling interval determination, optional resource enumeration or discovery.
Bases: ceilometer.pipeline.Pipeline
Represents a pipeline for Samples.
Bases: ceilometer.pipeline._PipelineTransportManager
Bases: ceilometer.pipeline.Sink
Bases: ceilometer.pipeline.PipelineSource
Represents a source of samples.
In effect it is a set of notification handlers processing samples for a set of matching meters. Each source encapsulates meter name matching and mapping to one or more sinks for publication.
Bases: object
Represents a sink for the transformation and publication of data.
Each sink config is concerned only with the transformation rules and publication conduits for data.
In effect, a sink describes a chain of handlers. The chain starts with zero or more transformers and ends with one or more publishers.
The first transformer in the chain is passed data from the corresponding source, takes some action such as deriving rate of change, performing unit conversion, or aggregating, before passing the modified data to next step.
The subsequent transformers, if any, handle the data similarly.
At the end of the chain, publishers publish the data. The exact publishing method depends on publisher type, for example, pushing into data storage via the message bus providing guaranteed delivery, or for loss-tolerant data UDP may be used.
If no transformers are included in the chain, the publishers are passed data directly from the sink which are published unchanged.
Bases: object
Represents a generic source