Skip to content

StatsAgg v1.4
Compare
Choose a tag to compare
@jds86930 jds86930 released this 20 Aug 22:15
· 392 commits to master since this release
v1.4
3abd911
  • Added support for receiving & outputting InfluxDB metrics
    • The metric format used in InfluxDB 0.6x, 0.7x, and 0.8x is supported (just in time for it to be depreciated)
    • The metric format used in InfluxDB 0.9x will be supported in the next StatsAgg release
  • Added support for 'sanitizing' Graphite & OpenTSDB metrics on output. This setting is unique to each output module instance.
  • Metric groups can now 'blacklist' metrics via regular expressions. When a metric is 'blacklisted' in a metric group, it will not represent itself as being a match for the metric group (and therefore cannot be alerted on).
  • Added support output via OpenTSDB HTTP/JSON
    • Previously, StatsAgg could only output to OpenTSDB via telnet
  • Improved shutdown time & safety
  • For output modules, added configurable connection timeouts & read timeouts
  • Improved timeout & retry behavior for all output modules
  • Added a description field to 'alert suspensions'.
  • Added 'time unit' fields to 'Alert' & 'Alert Suspension' configurations. These apply to fields like 'duration'.
  • 'Positive alert' notification groups are now a separate field of an 'Alert'.
  • New 'Clear All' button in the WebUI on 'AlertAssociations'. This can be used to clear/remove triggered availability alert metrics en masse
  • Added the (configurable) ability to limit the maximum number of concurrently outputting output modules (spanning all output modules).
    • If one tries to initiate and output module when the maximum number of concurrently output modules already running, then a warning will be thrown and the output request will be discarded.
    • This helps safeguard StatsAgg from output endpoints that are experiencing availability or performance issues.
  • Added the ability to limit the maximum number of currently outputting output modules for specific output modules (ex -- OpenTSDB HTTP #2).
    • If one tries to initiate and output module when the maximum number of concurrently output modules already running (of that specific output module), then a warning will be thrown and the output request will be discarded.
    • This helps safeguard StatsAgg from output endpoints that are experiencing availability or performance issues.
  • Removed the 'send previous metric' feature for Graphite, OpenTSDB, and InfluxDB metrics. It was recommended to be disabled, the data wasn't persisted, and it was hard to maintain, and no one used it.
  • The application configuration fields 'alert_output_alert_status_to_graphite' & 'alert_output_alert_status_to_graphite_metric_prefix' have been renamed to reflect that StatsAgg supports outputting to many database technologies.
    • alert_output_alert_status_to_graphite -> alert_output_status
    • alert_output_alert_status_to_graphite_metric_prefix -> alert_output_status_metric_prefix
    • If you have customized these fields, then you will have to rename the relevant field(s) in your application.properties file
  • I missed the memo that said the plural form of regex is 'regexes', so I changed the 'regexs' to 'regexes' everywhere in the code, database, & WebUI.
  • Updated most Java & Javascript libraries
  • Java 1.8+ is now required for StatsAgg. Java 1.7 has been end-of-life for several months, and it isn't worth maintaining backward compatibility
  • Initial implementation of an API layer. This will be refined/expanded on in future versions of StatsAgg.
  • If you upgrading from a previous version of StatsAgg, then you will need to run the SQL found in "Upgrade to 1.4.txt" against your StatsAgg database
    • Located @ StatsAgg\WEB-INF\sql
Assets 3
Loading