Monitoring Spring Boot

Supported versions

Instana supports Spring Boot 1.x, 2.x and 3.x.

Supported operating systems

The supported operating systems of Spring Boot sensor are consistent with host agents requirements, which can be checked in the Supported operating systems section of each host agent, such as Supported operating systems Linux.

Supported tracing

For this technology, Instana supports tracing. For more information, see Instrumented frameworks and libraries.

Enabling JMX

For Spring Boot 2.2.x and later, you must enable Java Management Extensions (JMX) in the application.properties file by setting the following property:

spring.jmx.enabled=true

Exposing the Spring Boot management MBeans

If the endpoints are disabled in the application.properties file with the following configuration settings, then you need to expose the Spring Boot management MBeans because sensor depends on the MBeans to collect metrics from the Spring Boot application:

management.endpoints.enabled-by-default=false

You can expose the Spring Boot management MBeans by enabling the following endpoints:

management.endpoint.info.enabled=true
management.endpoint.health.enabled=true
management.endpoint.metrics.enabled=true
management.endpoint.env.enabled=true

Instana queries metrics from the Spring Boot management MBean org.springframework.boot:type=Endpoint,name=Metrics, and you do not need to configure the authentication or credentials for secured actuator endpoints.

Setting health-interval parameter

By default, Instana queries the health of the Spring Boot app every 10 minutes by querying the management MBean org.springframework.boot:type=Endpoint,name=Health.

If needed, you can configure the desired health-interval parameter in seconds:

com.instana.plugin.springboot:
  health-interval: 30

The health check can introduce new downstream calls, depending on the health check implementation. If the health check fails, then you see a warning message that indicates the root cause.

Exposing endpoints over HTTP

For Spring Boot 2 and later, Spring Boot Actuator provides dependency management and auto-configuration for Micrometer. Depending on the Spring Boot version, different Micrometer metrics are available on the JVM dashboard.

You must carefully consider when to expose the endpoints over HTTP because endpoints might contain sensitive information. By default, only the health endpoint is exposed. For more information, see Exposing Endpoints.

To exclude specific endpoints from HTTP, use the following directive:

management.endpoints.web.exposure.exclude=health,info

To exclude all endpoints from HTTP, use the following directive:

management.endpoints.web.exposure.exclude=*

Note: For Spring Boot 3.x, make sure that the following directive is available in the application.properties file:

management.endpoints.jmx.exposure.include=env,health,info,metrics

Before the application configuration properties can be displayed in the Instana UI, you need to make extra changes in the application.properties file. Otherwise, these properties are shown as ****** because of sensitive values. For more information, see Sanitize Sensitive Values.

To always show the values as clear text, use the following configuration in the application.properties file:

management.endpoint.env.show-values=ALWAYS

Naming Spring Boot apps

Instana extracts the name for the Spring Boot instances by using the build-info.properties file. This file can be generated, for example, with spring-boot-maven-plugin:

<plugin>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-maven-plugin</artifactId>
  <configuration>
    <executable>true</executable>
  </configuration>
  <executions>
    <execution>
      <goals>
        <goal>build-info</goal>
      </goals>
      <configuration>
        <additionalProperties>
          <name>${project.artifactId}</name>
          <version>${project.version}</version>
        </additionalProperties>
      </configuration>
    </execution>
  </executions>
</plugin>

For more information about Integrating with Actuator, see Spring Boot Maven Plugin Documentation.

For Spring Boot 3, set the spring.application.name property in your application configuration.

Endpoints and HTTP sessions

Datasources

Health Signatures

For each sensor, a curated knowledgebase of health signatures is evaluated continuously against the incoming metrics and is used to raise issues or incidents that depend on the user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any selected entity.

For more information about built-events for the Spring Boot sensor, see the Built-in events reference.

Spring Boot Actuator is not configured

Monitoring issue type: springboot_actuator_not_configured

To configure Spring Boot Actuator, see Configuring Spring Boot Actuator.

JMX is not enabled

Monitoring issue type: springboot_jmx_not_enabled

To enable JMX, see Configuring Spring Boot Actuator.