- 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

- Fixing a few warnings here and there in the tools subdirectory

- Name uniqueness checks have been extended to sensor names and sensor
groups (managed by two separate sets)

- Sensor caches across DCDB are now managed by the CacheEntry
implementation under "common"
- Provides utility methods to perform averages, checks, get views etc.
- SensorCache class in collectagent kept due to its libdcdb dependencies

- We enforce that instantiated analyzers have unique names
- The checks are carried out by the MQTTChecker class, which maintains
group/analyzer names in a separate sets with respect to MQTT topics

- Checks on MQTT topics have been made generic in the MQTTChecker singleton
class under "common"
- MQTT topic checks are now performed also when plugins are reloaded; if
the checks fail, the plugin is cleared and left uninitialized
- All sensors in a plugin not satisfying the checks are logged now, not
only the first one
- Fixed a minor bug that resulted in msgrates of 0 under certain
compilers, due to type promotion in C++

- Removed dependencies from data analytics framework to dcdbpusher
- Checks for correctness of MQTT topics moved to the mqttChecker shared class

- Fixed some linking issues with the SensorNavigator
- dcdbpusher now uses the common logging interface to setup file and
command-line sinks

- Added a 'common' directory where all shared code has been placed
- Analytics package has been moved out of dcdbpusher, now has its own makefile
- Some renaming here and there for uniformity

Msr

See merge request dcdb/dcdbpusher!2

- Fixed a minor issue that caused text corruption when using the -h
option on certain shells
- Collectagent now exits gracefully also when receiving a SIGTERM signal

- Using the "delay" parameter, analyzers can be started in a delayed way
- Useful to let sensor caches fill and prevent errors being thrown

- Setting a maxMsgNum of -1 will result in the minimum possible value
(slightly above the predicted message rate) being picked as a cap
- Added some logging to make the feature more verbose

- Added configuration options to tune the Cassandra driver for
optimal performance
- Added a "debugLog" configuration switch that enables logging of
errors in asynchronous inserts in the Cassandra driver

Changes to handle conflict with monitoring: 1. we check if counters are already running, and just read them if this is the case. 2. we program them if they are not running. 3. When dcdb stops, they are left running for other agents like EAR.

- The CollectAgent sensor cache is automatically purged each X seconds
(X is configurable through the cleaningInterval parameter), deleting
all entries than have not been updated in the last X seconds
- Fixed some minor bugs related to index management in sensor caches

-check if counters already enabled before programming them
-reset counters if stopped

- Cache interval was previously not correctly set

- Fixes to minor bugs that kept the plugin from compiling

- Implemented a check in MQTTPusher that prevents the main publish
loop from being invoked anytime mosquitto_loop returns, but only once
every second at most