Bases: object
Represents a coupling between a sink and a corresponding source.
Bases: exceptions.Exception
Bases: object
Pipeline Manager
Pipeline manager sets up pipelines according to config file
Usually only one pipeline manager exists in the system.
Build a new Publisher for these manager pipelines.
Parameters: | context – The context. |
---|
Bases: object
Bases: object
Represents a sink for the transformation and publication of samples.
Samples are emitted from a related source.
Each sink config is concerned only with the transformation rules and publication conduits for samples.
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 samples from the corresponding source, takes some action such as deriving rate of change, performing unit conversion, or aggregating, before passing the modified sample 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 samples UDP may be used.
If no transformers are included in the chain, the publishers are passed samples directly from the sink which are published unchanged.
Flush data after all samples have been injected to pipeline.
Bases: object
Represents a source of samples.
In effect it is a set of pollsters and/or notification handlers emitting samples for a set of matching meters. Each source encapsulates meter name matching, polling interval determination, optional resource enumeration or discovery, and mapping to one or more sinks for publication.