You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/10 10:55:04 UTC

[jira] [Resolved] (CAMEL-5104) [GSoC 2012] Alerts support

     [ https://issues.apache.org/jira/browse/CAMEL-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5104.
--------------------------------
    Resolution: Won't Fix

> [GSoC 2012] Alerts support
> --------------------------
>
>                 Key: CAMEL-5104
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5104
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, camel-snmp, jmx
>            Reporter: MichaƂ Warecki
>            Priority: Minor
>              Labels: gsoc2012
>             Fix For: Future
>
>   Original Estimate: 2,016h
>  Remaining Estimate: 2,016h
>
> I think this functionality can help Camel meet some of the requirements of mission-critical systems.
> Alerts are kind of events which may indicate threat to the proper functioning of the integration platform such as:
> - specified thread pool reaches a specified threshold ratio (http://camel.apache.org/threading-model.html),
> - low memory (i.e. 70% Perm Gen is used),
> - specified URL location is invalid (i.e. returns specified code),
> - specified JMX attribute has specifies value (it really can be a point to custom alert guard),
> - specified exception type occurs (i.e. IOException may be caused by lack of disk space),
> - route did not finish its execution within specified period of time,
> - some specified expression based on headers values.
> Alerts should send predefined notifications (configured by standard Camel components like SMTP or SNMP). Additionally, it should be possible to set severity level of alert.
> See nabble: http://camel.465427.n5.nabble.com/DISCUSS-Camel-Alerts-td5497221.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)