- Fixed name of log files for collectagent
- Fixed a few compilation warnings under gcc 7
- README for dcdbpusher now correctly refers to dcdbpusher.conf files
- SensorNavigator is rebuilt after plugin reloads only if data analytics
are currently running

- The multiplier used when computing percentages in the SAR ProcFS
parser has been raised to 100000 to reduce accuracy loss

- Fixed a couple minor bugs arising when only one column is selected
in the stat file
- Fixed a bug in the SAR parser

# Conflicts:
#	.gitignore

- Added the htVal parameter to the copy constructor

- a "filter" configuration parameter has been added, which is used
to discard sensor names when building the sensor navigator
- Can be used to e.g. build a sensor navigator in a collectagent
using only the sensors that are directly collected by it
- Implemented a switch to select leftmost/rightmost binary search
in CacheEntry, used for the QueryEngine

Change perf-plugin implementation: Instead of duplicating sensorGroups per CPU only one group is used with duplicated sensors

- Fixed a few warnings introduced in the latest ProcFS commit

- Virtual threads can now be automatically aggregated for procstat and
sar groups
- the htVal parameter is the number of physical threads; corresponding
virtual threads are determined via modulo arithmetic
- Minor changes to AnalyticsController in collectagent

- 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

- Parsing of host:port network addresses is handled by GlobalConfiguration
- -p dcdbpusher command line parameter (broker port) removed and integrated
into the -b argument

- 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

- When performing sensor queries with absolute timestamps (rel=false) a
binary search algorithm is used to compute the bounds of the required
sensor cache view
- This is more accurate than the fuzzy method employed with relative
timestamps (rel=true)

(cherry picked from commit 2436f553)

- The REST API of the data analytics framework is now functional in
the collectagent as well
- This implementation is temporary and should be replaced with a generic
REST API server whenever possible

Add SensorConfig::loadCache() that loads all published sensors into a list and creates a map for faster lookup of sensor names

- Batch size in the collectagent now taken into account to determine if
a specific sensor cache is stale or not

- Integration of data analytics framework in collectagent complete
- REST API integration still pending
- Added some documentation to the code

- QueryEngine integration done (but not functional yet, debugging required)
- Changed behavior on exceptional conditions: if SensorNavigator or
AnalyticsManager initialization fails, termination follows
- Now the QueryEngine can also access output sensors of other Analyzers
- Minor bugfixes

- First step for integration of the analytics framework in the collectagent
- QueryEngine and REST API integration still missing
- Proper testing still to be done
- Added a probe function: the global config file is scanned before
initialization, and if no data analytics plugins are requested, no
sensor navigator is built