GitLab

- Fixed a bug in the Filesink plugin that caused occasional crashes
- Fixed a bug in the Pusher REST API that prevented plugin reloads
for operators

- Make clean might be required

-fixed symbol address calculation

- 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

-implement custom symbollookup instead of Caliper service usage
-relocate lookup logic to pusher plugin
-share symbol information via shared memory

- Added shuffling of data in the training set in an attempt to improve
regression accuracy

-avoids symbollookup service but instead uses dladdr
-not fully re-entrant but does not crash
-needs huge clean-up

- The "observations" operation simply counts the number of total queried
elements over the inputs of each unit

- Fixed a bug in UnitGenerator when generating units in relaxed mode
- Added the latest reading as feature in the Regressor plugin
- Added a small delay in the scheduling of analyzers to give higher
priority to standard monitoring plugins

- 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

- on sampling event record current object file + function name
- add numa-node and cpu info

- If getImportances is set to true, the regressor will print a sorted
list of features and their importances, after performing training
- A REST action to retrieve the same list has been added

- When the start and end timestamps of a query are equal, it is enforced
that only one sensor value will be retrieved

- Staleness checks when performing sensor queries in the cache are
now enforced both in relative and absolute modes
- Fixed a race condition causing wrong results when performing queries
in absolute mode
- Changed logging in the TesterAnalyzer plugin