Edit

Collect Spring Cloud Resilience4J Circuit Breaker Metrics with Micrometer (Preview)

  • Article
  • 2 minutes to read

Note

Azure Spring Apps is the new name for the Azure Spring Cloud service. Although the service has a new name, you'll see the old name in some places for a while as we work to update assets such as screenshots, videos, and diagrams.

This article applies to: ✔️ Basic/Standard tier ✔️ Enterprise tier

This article shows you how to collect Spring Cloud Resilience4j Circuit Breaker Metrics with Application Insights Java in-process agent. With this feature you can monitor metrics of resilience4j circuit breaker from Application Insights with Micrometer.

We use the spring-cloud-circuit-breaker-demo to show how it works.

Prerequisites

Build and deploy apps

The following procedure builds and deploys apps.

  1. Clone and build the demo repository.
git clone https://github.com/spring-cloud-samples/spring-cloud-circuitbreaker-demo.git
cd spring-cloud-circuitbreaker-demo && mvn clean package -DskipTests
  1. Create applications with endpoints
az spring app create
    --resource-group ${resource-group-name} \
    --name resilience4j \
    --service ${Azure-Spring-Apps-instance-name} \
    --assign-endpoint
az spring app create \
    --resource-group ${resource-group-name} \
    --service ${Azure-Spring-Apps-instance-name} \
    --name reactive-resilience4j \
    --assign-endpoint
  1. Deploy applications.
az spring app deploy -n resilience4j \
    --jar-path ./spring-cloud-circuitbreaker-demo-resilience4j/target/spring-cloud-circuitbreaker-demo-resilience4j-0.0.1.BUILD-SNAPSHOT.jar \
    -s ${service_name} -g ${resource_group}
az spring app deploy -n reactive-resilience4j \
    --jar-path ./spring-cloud-circuitbreaker-demo-reactive-resilience4j/target/spring-cloud-circuitbreaker-demo-reactive-resilience4j-0.0.1.BUILD-SNAPSHOT.jar \
    -s ${service_name} -g ${resource_group}

Note

  • Include the required dependency for Resilience4j:

    <dependency>
    <groupId>io.github.resilience4j</groupId>
    <artifactId>resilience4j-micrometer</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-circuitbreaker-resilience4j</artifactId>
</dependency>

  • The customer code must use the API of CircuitBreakerFactory, which is implemented as a bean automatically created when you include a Spring Cloud Circuit Breaker starter. For details see Spring Cloud Circuit Breaker.

  • The following 2 dependencies have conflicts with resilient4j packages above. Be sure the customer does not include them.

    <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-sleuth</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-zipkin</artifactId>
</dependency>

Navigate to the URL provided by gateway applications, and access the endpoint from spring-cloud-circuit-breaker-demo as follows:

/get
/get/delay/{seconds}
/get/fluxdelay/{seconds}

Locate Resilence4j Metrics from Portal

  1. Select the Application Insights Blade from Azure Spring Apps portal, and select Application Insights.

    resilience4J 0

  2. Select Metrics from the Application Insights page. Select azure.applicationinsights from Metrics Namespace. Also select resilience4j_circuitbreaker_buffered_calls metrics with Average.

    resilience4J 1

  3. Select resilience4j_circuitbreaker_calls metrics and Average.

    resilience4J 2

  4. Select resilience4j_circuitbreaker_calls metrics and Average. Select Add filter, and then select name as createNewAccount.

    resilience4J 3

  5. Select resilience4j_circuitbreaker_calls metrics and Average. Then select Apply splitting, and select kind.

    resilience4J 4

  6. Select resilience4j_circuitbreaker_calls, `resilience4j_circuitbreaker_buffered_calls, and resilience4j_circuitbreaker_slow_calls metrics with Average.

    resilience4J 5

Next steps