Analysis of the whole process of SpringBoot application accessing Prometheus

Prometheus: Prometheus is an open monitoring solution. Users can easily install and use Prometheus and expand it

The following will implement the whole process of a SpringBoot application accessing Prometheus

1.2 installation

Linux Installation

  • Download package specified on the official website:

Download local installation startup


tar -zxvf prometheus-2.26.0.linux-amd64.tar.gz
cd prometheus-2.26.0.linux-amd64

# Start command

After startup, local access You can see the interface provided by default

2. SpringBoot application access

The SpringBoot we demonstrated is 2.0 +, so choose directly   io.micrometer   It depends on the package; Lower versions cannot use this pose, but can directly use the officially provided client; There is no extension here

2.1 dependency configuration

Spring boot's actor is used to provide extension endpoints (so Prometheus's pull mode is adopted in this paper)

SpringBoot version is   2.2.1.RELEASE

Core dependency




yaml configuration file. You need to specify parameters related to Prometheus. A demo is as follows

    name: prometheus-example
        include: "*"
      application: ${}

be careful

  • management.endpoints.web.exposure.include   All web interfaces specified here will be reported
  • metrics.tags.application   This app will bring all reported metrics   application   This label

After the above configuration is completed, a  / actuator/prometheus   For Prometheus to pull Metrics information

2.2 application startup

For SpringBoot, there is no need to do anything else to report the basic information of the application

A simple demo is as follows

public class Application {
    private Random random = new Random();
    // An http interface for demonstration
    @GetMapping(path = "hello")
    public String hello(String name) {
        int sleep = random.nextInt(200);
        try {
        } catch (InterruptedException e) {
        return "hello sleep: " + sleep + " for " + name;

    public static void main(String[] args) {;

    // Note that this is the core code block for registration
    MeterRegistryCustomizer<MeterRegistry> configurer(@Value("${}") String applicationName) {
        return (registry) -> registry.config().commonTags("application", applicationName);

At this point, the monitoring of springboot application is completed; Next, configure the server of prometheus

3. prometheus configuration and measurement

Under the package downloaded earlier, there is a configuration file   prometheus.yml  , Add a new Job

- job_name: 'prometheus-example'
true# Grab frequency
  scrape_interval: 5s
  # Grab endpoint
  metrics_path: '/actuator/prometheus'
  	# The target machine, array, supports cluster pull
    - targets: ['']

After modifying the configuration, you need to restart. After the service is started, you can our application information on the console

Next, access Graph and select metric:
http_server_requests_seconds_count   You can see a record of picking up metric

We defined a Controller earlier, then simply access it several times, and then take a look, you will find another record

These data are directly integrated by the framework layer to report the relevant information of the REST interface. With this metric, we can realize the statistics of qps

3.1 qps statistics


  • rate: used to count the growth trend. The Metric to be reported is of Counter type (only increase but not decrease)
  • irate: similar to rate, the difference is that rate counts the average growth rate over a period of time and cannot reflect the emergencies (i.e. instantaneous peak) in this time window. irate calculates the growth rate through the last two sample data in the interval vector, but when the selected interval range is large, it may cause no small deviation
  • Sum: sum, applicable to statistical scenarios

For more built-in functions, please refer to PromQL built-in functions

3.2 time consuming statistics

In addition to qps, another indicator that we often pay attention to is rt. for example, the average rt of the above interface is realized through the combination of two metrics

sum(rate(http_server_requests_seconds_sum{application="prometheus-example"}[10s])) / sum(rate(http_server_requests_seconds_count{application="prometheus-example"}[10s]))

After removing the sum aggregation, you can see the access of each interface

4. Grafana market configuration

Panel monitoring is more powerful than grafana. In particular, grafana itself provides many templates that can be imported directly

For installation, please refer to: 210318 Linux grafana disk access mysql

4.1 market configuration

After grafana starts, configure the data source Promethues

Next, configure the application configuration panel of SpringBoot, and you can directly use the ready-made template, such as 12856

After importing, the market is shown as follows

Let's take a look at the statistics promql of request time-consuming

4.2 where can I find the large-scale formwork

How to find the directly available market?

  • You can find it on the market on the official website
  • As
  • Select one, click in, the one on the right   Copy ID toClipboard   The corresponding number is what we need

5. Summary

After the whole process, you will find that the cost of accessing Prometheus in SpringBoot project is very low. Basically, there is not much coding work. You can configure it to the monitoring market with a full set of functions. Don't be too high

The convenience of high encapsulation is very prominent here, but after doing it, recall what I got?

It seems that I haven't got anything. If my service only provides grpc/dubbo interface, let's access the monitoring now. It seems that we are still blind. How should I play? (welcome to leave a message in the comment area)

Original link: Integrating Prometheus for application monitoring/

  For more information, you can pay attention to the official account "w's programming diary" and reply to Java for more information.

Keywords: Java Spring Interview Programmer

Added by benson on Wed, 24 Nov 2021 09:00:32 +0200