GitLab

- Allows to encode "not set" states for single members

- Basic implementation that allows to publish sensors as operations
of other sensors
- Still not functional and untested

- The interval field now defaults to the value inherited from the
sensor groups that the sensor belongs to
- Metadata blocks in templates can now be overwritten completely or
only in part

- Also added a "pattern" field to SensorMetadata class for consistency
with the DCDB::PublicSensor class

- Data is correctly parsed from DCDBPusher, sent as JSON, and received
by collectagents
- Integration in libdcdb is still pending

- The configurator now accounts for hierarchical units
- Added checks in existing plugins to enforce flat/hierarchical units
- DISCLAIMER: this has likely broken the framework until I refactor OperatorTemplate

- Added generateFromTemplate method
- Fixed handling of special cases (on-demand and root units)
- Added enforceTopics option to force a MQTT prefix for unit outputs
- printConfig in UnitTemplate now accounts for hierarchical units
- Updated README

- Streamlined the public interface
- Added methods for single and multiple unit generation (plain and hierarchical)
- Added methods to automatically tell whether to build plain or hierarchical units
- Added pointer to parent in UnitTemplate
- Added methods to distinguish top and subunits in UnitTemplate

- Integrated the "disabled" parameter for operators
- "operatorPlugin" can be left empty if path and config are default
- "operatorPlugin" config field is relative to _cfgPath if not absolute
- Relaxed the operator name uniqueness constraint, duplicated operators
now have (again) all the same name
- Minor bugfixes

- Fixed a bug that prevented pipelines in collectagent deployments
- Incremented the tolerance threshold of fuzzy queries to 1h
- Fixed the assignment of MQTT topics to job sensors

- If a subSampling value of 0 or lower is chosen for a sensor, it will
never be pushed out over MQTT/Cassandra and only kept in memory

- Fixed a bug that prevented relaxed mode from working properly for
operators deployed on the collectagent
- Changed the function of the "delay" parameter: it now specifies a
fixed offset applied to the computation interval of each operator,
useful to tune the flow of data in operator pipelines

- An operator naming conflict prevented the option from working correctly

- Make clean might be required

- This plugin allows to write arbitrary sensor data to the local file system
- Removed the obsolete sink functionality in SensorBase
- Also fixed a minor bug concerning MQTT topic assignment in template analyzers

- Allowing users to define analyzers with inputs but no outputs
- In this case, a "sink" unit is created, which always refers to the
root of the sensor tree
- This is useful for control analyzers that tune system knobs but do
not actively produce sensor data

- For plugins that use hierarchical units (e.g., job analyzers) a
"flatten" plugin option was added. If enabled, output sensors in the
sub-units of each unit will be exposed as well, and their output values
propagated
- Minor fixes here and there

- Fixed a fair amount of bugs related to job analyzers
- Added a "getJobsInIntervalRunning" method to JobDataStore, to get
the list of jobs that were running in a certain time interval
- Some code refactoring for the JobDataStore class to reduce duplication
- Job analyzers have been tested and are working properly as of now

- Now supports also standard deviation and percentile computation
- Multiple output sensors per analyzer can be defined, each performing
a different aggregation task
- QueryEngine has been slightly modified so as not to clear the input
sensor reading buffer (if any), thus allowing to accumulate sensor
values with subsequent calls

- New method is lock-based and compatible with all features (e.g. REST API)
in the framework
- Performance impact is expected to be negligible as race conditions will
not be frequent

- Template for Job Analyzers, derived from AnalyzerInterface

- String topics are now used across all of DCDB, up to Cassandra
- As of now, sensor names ALWAYS match MQTT topics
- Users can still define sensor "aliases" via dcdbconfig that point
to the same topics

- Update config files to reflect new topic structure
- Updated READMEs accordingly
- Added support for "relaxed" analyzers, whose units can be built
even if some sensors cannot be found in the system
- Added support for sub-units, so as to build hierarchical unit structures

- Textual MQTT topics working in dcdbpusher and data analytics framework
- REST API still not working properly
- Testing on the collectagent not performed yet

- Now template sensors can be defined in data analytics plugins, and
can be used both for input and output
- The list of input "prototype" sensors of a template analyzer is now
propagated to derived analyzers
- The list of output "prototype" sensors of a template is ignored and
not inherited, because it would interfere with the Unit system

- The GlobalConfiguration class includes all shared logic to read and
parse configuration attributes for the collectagent and dcdbpusher
- The class is further expanded to add application-specific
configuration parameters and blocks

- Auto-publish is now case insensitive with respect to the <sensor> and
<group> patterns
- If an invalid pattern was specified (missing <sensor> clause) the
configuration is aborted
- Checks for the uniqueness of sensor and group names have been
temporarily dropped as they interfere with templates and entities
(until we find a good solution for MQTT topics)

- Added some more indentation to make the configurations more readable
- Fixed one more warning in dcdbquery

- Boolean configuration options now all accept "true" and "on" keywords
- Cache interval and thread count parameters removed from the command-line
interface for consistency; these can still be set in the config files
like all other parameters
- global.conf file renamed to dcdbpusher.conf for consistency