[
https://issues.apache.org/jira/browse/CAMEL-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016515#comment-18016515
]
Dylan Piergies edited comment on CAMEL-18597 at 8/27/25 12:14 PM:
------------------------------------------------------------------
I would suggest a slightly different approach, more closely aligned with the
metrics that Resilience4J (and presumably others) make available.
1. Attach state transition listeners and output log messages, rather than
metrics, when a state transition occurs.
2. Expose Micrometer metrics for values where metrics make more sense, e.g.
gauges for success/failure rates, slow call rates, etc, tagged with the route
ID, node ID, Camel context name, etc.
was (Author: JIRAUSER291704):
I would suggest a slightly different approach, more closely aligned with the
metrics that Resilience4J (and presumably others) make available.
1. Attach state transition listeners and output log messages, rather than
metrics, when a state transition occurs.
2. Expose metrics for values where metrics make more sense, e.g. gauges for
success/failure rates, slow call rates, etc, tagged with the route ID, node ID,
Camel context name, etc.
> Make Circuit Breakers and friends observable
> --------------------------------------------
>
> Key: CAMEL-18597
> URL: https://issues.apache.org/jira/browse/CAMEL-18597
> Project: Camel
> Issue Type: New Feature
> Components: camel-micrometer
> Reporter: Marco Bungart
> Priority: Minor
> Fix For: Future
>
>
> I would like to be able to monitor the state of my Circuit Breakers, as well
> as related elements, e.g. ThrottlingExceptionRoutePolicy.
> Thus, the state of such components should be exported in a standardized
> manner (e.g. through micrometer), so I can automate monitoring and altering.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
