[
https://issues.apache.org/jira/browse/KARAF-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072421#comment-17072421
]
ASF subversion and git services commented on KARAF-5741:
--------------------------------------------------------
Commit 3ece653e3c5e7540408f21707dc7eacefa74bcde in karaf-decanter's branch
refs/heads/master from jbonofre
[ https://gitbox.apache.org/repos/asf?p=karaf-decanter.git;h=3ece653 ]
[KARAF-5741] Complete refactoring of the alerting service allowing
multi-properties and time query support
> Improve Decanter alerting by supporting time series and multi-attributes
> ------------------------------------------------------------------------
>
> Key: KARAF-5741
> URL: https://issues.apache.org/jira/browse/KARAF-5741
> Project: Karaf
> Issue Type: Improvement
> Components: decanter
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: decanter-2.3.0
>
>
> We did good improvement on Decanter alerting in 2.0.0 release.
> I would like to include the following improvement for 2.1.0:
> - be able to store some events (defined in the matcher) with the timestamp in
> order to do alerting based on time. For instance: I saw this pattern three
> times in the last hour, or this attribute is in this range in the last 10mn.
> - improve the checker syntax. Instead of a single line, I'm proposing to use
> JSON to describe the alert pattern. It will allow us to have multi-attribute
> matcher and different filter. For instance:
> {code}
> { "attributes" : ["ObjectName:*foo*", "QueueSize:*"],
> "alert": { "type":"greater","value":"0"},
> "time":"now"}
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
