Time series monitoring and alerting platform.
Argus 2.21.3 release is in production. Here are the features/changes released
Ajna consumer changes to eliminate duplicate values with the same timestamp. Metric meta data indexing improvements to identify high cardinality metrics Improvements to metric discovery query time Enforce max datapoints limit on fill transform output Bug fix NO_DATA trigger not firing when expression is wrapped in SUM transform Templatize notification fields of alerts Bug fix . Alert notification message at times is saying alert is triggered even though alert is cleared Metric name length restriction to 255 character.
scopenames
and scopemetricnames
and update if create fails. This will populate cts
field1.Add Oauth Support for Authentication 2.Customized argus alert trigger name 3. Formatting changes for Alert notification
Alert scheduling improvements - a. Reduce the alert scheduling interval from 15 minutes to 1 minute b. Cache alert definitions during scheduling for better performance c. Schedule by grouping cron expressions and predetermining which alerts need to be run at a particular minute, instead of relying on quartz scheduler. d. Add more KPIs to better track the alert scheduler performance
Alert evaluation improvements - a. Caching notification cooldown and trigger status locally on alert clients to prevent too many queries being made to postgres b. Created a whitelist of scopes for which the alerts will not be disabled during a data lag
Add metrics to track usage of discovery service and TSDB service by user
Track Discovery queries that is above a configurable static threshold
Make bloom filter parameters configurable Flush bloom filter at fixed time of day based on configurable property
Minor bug fixes and optimizations
1.Bug fix: unable to render alert list after edit an alert 2.Allow UI to read big numbers in current locale 3.Fix conflicting logger implementations error 4.Add modified timestamp field while indexing in Elastic Search to allow purging of metric schema 5.Addressed third party library vulnerabilities. 6.Add a configurable TSDB Read ConnectionReuseStrategy 7.Add new metrics for quota / debugging 8.Use BloomFiliter for caching in schema clients replacing the existing trie