---
title: "Spring Boot integration | Grafana Cloud documentation"
description: "Learn about Spring Boot Grafana Cloud integration."
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

# Spring Boot integration for Grafana Cloud

Spring Boot is Spring’s convention-over-configuration solution for creating stand-alone, production-grade Spring-based Applications. This integration enables Grafana Alloy to send metrics to Grafana Cloud along with a useful default dashboard for visualization.

The provided dashboard is a modified version of the [Spring Boot Statistics](/grafana/dashboards/6756) community dashboard.

This integration includes 1 pre-built dashboard to help monitor and visualize Spring Boot metrics.

## Before you begin

The Spring Boot application must have the [actuator](https://docs.spring.io/spring-metrics/docs/current/public/prometheus) enabled.

Please see the [demo application](https://github.com/grafana/spring-boot-demo) for details.

We have added a custom label to the dashboard to help you observe multiple applications. To use it, make sure to add a line of code like the following in your `@SpringBootApplication` class to include an `application` label to your metrics. Please change `MYAPPNAME` value accordingly. This is also present in the demo application.

java ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```java
@Bean
MeterRegistryCustomizer<MeterRegistry> metricsCommonTags() {
    return registry -> registry.config().commonTags("application", "MYAPPNAME");
}
```

## Install Spring Boot integration for Grafana Cloud

1. In your Grafana Cloud stack, click **Connections** in the left-hand menu.
2. Find **Spring Boot** and click its tile to open the integration.
3. Review the prerequisites in the **Configuration Details** tab and set up Grafana Alloy to send Spring Boot metrics to your Grafana Cloud instance.
4. Click **Install** to add this integration’s pre-built dashboard to your Grafana Cloud instance, and you can start monitoring your Spring Boot setup.

## Configuration snippets for Grafana Alloy

### Simple mode

These snippets are configured to scrape a single Spring Boot instance running locally with default ports.

First, **manually** copy and append the following snippets into your alloy configuration file.

### Metrics snippets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.relabel "metrics_integrations_integrations_spring_boot" {
	targets = [{
		__address__ = "localhost:1235",
	}]

	rule {
		target_label = "instance"
		replacement  = constants.hostname
	}
}

prometheus.scrape "metrics_integrations_integrations_spring_boot" {
	targets      = discovery.relabel.metrics_integrations_integrations_spring_boot.output
	forward_to   = [prometheus.remote_write.metrics_service.receiver]
	job_name     = "integrations/spring-boot"
	metrics_path = "/actuator/prometheus"
}
```

### Advanced mode

The following snippets provide examples to guide you through the configuration process.

To instruct Grafana Alloy to scrape your Spring Boot instances, **manually** copy and append the snippets to your alloy configuration file, then follow subsequent instructions.

### Advanced metrics snippets

Alloy ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```alloy
discovery.relabel "metrics_integrations_integrations_spring_boot" {
	targets = [{
		__address__ = "localhost:1235",
	}]

	rule {
		target_label = "instance"
		replacement  = constants.hostname
	}
}

prometheus.scrape "metrics_integrations_integrations_spring_boot" {
	targets      = discovery.relabel.metrics_integrations_integrations_spring_boot.output
	forward_to   = [prometheus.remote_write.metrics_service.receiver]
	job_name     = "integrations/spring-boot"
	metrics_path = "/actuator/prometheus"
}
```

To monitor your Spring Boot instance, you must use a [discovery.relabel](/docs/alloy/latest/reference/components/discovery.relabel/) component to discover your Spring Boot Prometheus endpoint and apply appropriate labels, followed by a [prometheus.scrape](/docs/alloy/latest/reference/components/prometheus.scrape) component to scrape it.

Configure the following properties within each `discovery.relabel` component:

- `__address__`: The address to your Spring Boot Prometheus metrics endpoint.
- `instance` label: `constants.hostname` sets the `instance` label to your Grafana Alloy server hostname. If that is not suitable, change it to a value uniquely identifies this Spring Boot instance.

If you have multiple Spring Boot servers to scrape, configure one `discovery.relabel` for each and scrape them by including each under `targets` within the `prometheus.scrape` component.

## Dashboards

The Spring Boot integration installs the following dashboards in your Grafana Cloud instance to help monitor your system.

- Spring Boot Statistics

**Spring Boot Statistics**

## Metrics

The most important metrics provided by the Spring Boot integration, which are used on the pre-built dashboard, are as follows:

- hikaricp\_connections
- hikaricp\_connections\_acquire\_seconds\_count
- hikaricp\_connections\_acquire\_seconds\_sum
- hikaricp\_connections\_active
- hikaricp\_connections\_creation\_seconds\_count
- hikaricp\_connections\_creation\_seconds\_sum
- hikaricp\_connections\_idle
- hikaricp\_connections\_pending
- hikaricp\_connections\_timeout\_total
- hikaricp\_connections\_usage\_seconds\_count
- hikaricp\_connections\_usage\_seconds\_sum
- http\_server\_requests\_seconds\_count
- http\_server\_requests\_seconds\_sum
- jvm\_buffer\_memory\_used\_bytes
- jvm\_buffer\_total\_capacity\_bytes
- jvm\_classes\_loaded\_classes
- jvm\_classes\_unloaded\_classes\_total
- jvm\_gc\_memory\_allocated\_bytes\_total
- jvm\_gc\_memory\_promoted\_bytes\_total
- jvm\_gc\_pause\_seconds\_count
- jvm\_gc\_pause\_seconds\_sum
- jvm\_memory\_committed\_bytes
- jvm\_memory\_max\_bytes
- jvm\_memory\_used\_bytes
- jvm\_threads\_daemon\_threads
- jvm\_threads\_live\_threads
- jvm\_threads\_peak\_threads
- logback\_events\_total
- process\_cpu\_usage
- process\_files\_max\_files
- process\_files\_open\_files
- process\_start\_time\_seconds
- process\_uptime\_seconds
- system\_cpu\_count
- system\_cpu\_usage
- system\_load\_average\_1m
- tomcat\_global\_error\_total
- tomcat\_global\_received\_bytes\_total
- tomcat\_global\_sent\_bytes\_total
- tomcat\_sessions\_active\_current\_sessions
- tomcat\_threads\_busy
- tomcat\_threads\_config\_max\_threads
- tomcat\_threads\_current\_threads
- up

## Changelog

md ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy

```md
# 1.0.0 - January 2024

* Make exception label matcher case insensitive in Response time panel
* Update version number for stable release

# 0.0.6 - November 2023

* Replaced Angular dashboard panels with React panels

# 0.0.5 - September 2023

* New Filter Metrics option for configuring the Grafana Agent, which saves on metrics cost by dropping any metric not used by this integration. Beware that anything custom built using metrics that are not on the snippet will stop working.
* New hostname relabel option, which applies the instance name you write on the text box to the Grafana Agent configuration snippets, making it easier and less error prone to configure this mandatory label.

# 0.0.4 - January 2023

* Adding Job filter and making filters All and Multi selectable

# 0.0.3 - September 2022

* Update dashboard panels descriptions.

# 0.0.2 - October 2021

* Update mixin to latest version:
  - Update queries to use $__rate_interval

# 0.0.1 - December 2020

* Initial release
```

## Cost

By connecting your Spring Boot instance to Grafana Cloud, you might incur charges. To view information on the number of active series that your Grafana Cloud account uses for metrics included in each Cloud tier, see [Active series and dpm usage](/docs/grafana-cloud/fundamentals/active-series-and-dpm/) and [Cloud tier pricing](/products/cloud/pricing/).