[jira] [Resolved] (CAMEL-8999) Watchdog route policy for spotting starved, overactive or stuck routes

["Claus Ibsen (Jira)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-8999.
--------------------------------
    Resolution: Abandoned

> Watchdog route policy for spotting starved, overactive or stuck routes
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-8999
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8999
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Jyrki Ruuskanen
>            Priority: Major
>             Fix For: Future
>
>
> In our use case we need to spot routes that are processing less than expected or too many exchanges in a certain time. The limits also depend on whether it is a busy or a quiet time (day vs night, weekdays vs weekend etc.).
> Also, we would like to be able to spot routes that are stuck but produce no errors.
> In my opinion the most natural solution is a RoutePolicy that would keep count of inflight and completed exchanges and perform periodic checks on this information. Multiple checks with different schedules would be allowed per RoutePolicy instance.
> If a check fails the RoutePolicy would log a warning. These warnings could then be singled out based on the logger by, for example, an automated log watcher.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)