Explain how spring boot admin uses Eureka monitoring service

preface

I'm just free recently. Let's learn how to build a spring boot admin environment. Many pits were encountered.

Most of the Internet is monitored directly by using admin URL, which is not flexible at all. This is not the result I want. Therefore, this article introduces the flexible monitoring program with the help of Eureka service registration and discovery function.

This paper mainly records the construction process of spring boot admin, hoping to be helpful. In fact, it's very simple. Don't be misled by the conventional way!

Environment introduction

Construction process

1. We don't need to make any changes to the previous Eureka client service, just keep the original state. 2. Set up the spring boot admin service (also a eureka service). 3 test result

Spring boot admin module

It must be noted here that so far (at 10:16 on October 31, 2017), we cannot use Eureka of edgware.build-snapshot version for spring boot admin, and an error will be reported because the latest version of codecentric1.5.4 is incompatible. Therefore, we need to downgrade the spring cloud version that admin depends on, and I use dalton.sr4. No problem!

POM file

application

@Enableadminserver is used to mark the application as admin

Other annotations are consistent with ordinary Eureka client applications

YML file

Result display

This is the end of the configuration. We start the applications of Eureka server, admin server and Eureka client ` ` Eureka client2 in turn

1. First go to the Eureka registry http://localhost:8761/ Check whether all apps have been registered

Our admin server is also registered as a service, so that we can play Eureka's service discovery function

2. View the monitoring UI in admin server http://localhost:8089

At this point, our spring boot admin has been built!

summary

The above port service name will vary according to your configuration. Please note

In addition, the version is also very noteworthy

There are also different methods used, so the configuration is also different. You must pay attention to your own implementation method

Source code in https://github.com/eumji025/spring-cloud-repository/tree/edgware