resilience4j | Circuit breaker , bulkhead , rate limiter | Dashboard library

After 10 hours of crazy debugging I had to replace yml to properties file and its started working.

I'm not sure why yml was unable to pick up the changes, surely its a bug!.

application.properties

I have noted the same problem after upgrading to SpringCloud 2020.0.2

Adding spring.cloud.config.enabled=false in the tests solved the issue.

E.g.:

As already answered in comments above RateLimiter tracks the number of subscriptions, not elements. To achieve rate limiting on elements you can use limitRate (and buffer + delayElements). For example,

Annotated methods must be public and not private.

How you are making parallel calls. Probably your requests are finishing too fast. To replicate the scenario. Lets have block in your api that takes computation time of 1 sec. Try to trigger the calls using JMeter or Apache Bench mark.

CallNotPermittedException and the underlying stack trace occur within the state machine logic after the breaker is opened, this is not the right place to look.

The events consumer buffer exposed through the actuator endpoint /actuator/circuitbreakerevents would list all the events within the breaker, what are errors, and the corresponding message.

https://resilience4j.readme.io/docs/getting-started-3#events-endpoint

It looks like you have a 5 x_y_z__resilience4j_circuitbreaker_state metrics for every name, each with a different kind label, one with a value of 1.0 and the others with a value of 0.0.

In this case if you do not expose 0.0 and a circuitbreaker changes through all states all metrics will report 1.0.

To reduce cardinality, you should remove the kind label and set the value to a state.

Instead of this:

We extended the documentation on running BAPI calls from the local machine. We added a section on how to maintain the environment variable destinations which lets the SAP Cloud SDK find the destination name.

Because of Spring AOP annotations don't work when you call a method, which is annotated, locally from the same class (bean), because then the PROXY is bypassed.

@Cacheable and @RateLimiter on the same method might not work, because of the Spring AOP Aspect order. See: https://docs.spring.io/spring-framework/docs/4.3.15.RELEASE/spring-framework-reference/html/aop.html#aop-ataspectj-advice-ordering

You can configure the order of the RateLimiter globally, but it might be better to move the method getFileName into another Bean und only use @RateLimiter.