Y77. Chapter IV Prometheus' monitoring system and practice -- Prometheus' service discovery mechanism (VIII)

8.prometheus Service discovery mechanism

prometheus By default pull To pull monitoring data , That is, go to the target host regularly to grab metrics data , Every captured target needs to expose one HTTP Interface ,prometheus Through this exposed interface, the corresponding index data can be obtained , In this way, the target server needs to decide which targets to collect , By configuring scrape_configs All kinds of job To achieve , Unable to dynamically perceive new services , If node or component information is added later , You have to modify it manually prometheus To configure , And restart prometheus, Very inconvenient , So there is dynamic service discovery , Dynamic service discovery can automatically discover new endpoints in the cluster , And add to the configuration , Discover through services ,prometheus You can find out what needs to be monitored Target list , And then poll these Target Get monitoring data .

prometheus Acquisition data source target There are many ways , Such as static configuration and service discovery configuration ,prometheus Support multiple service discovery ,prometheus There are many kinds of service discovery supported at present , Commonly used are mainly divided into the following ：

kubernetes_sd_configs：#kubernetes Service discovery , Give Way prometheus Dynamic discovery kubernetes Target monitored in 

static_configs：# Static service discovery , be based on prometheus The monitoring target specified in the configuration file 

consul_sd_donfigs：#Consul Service discovery , be based on consul Service dynamic discovery monitoring target 

file_sd_configs：# Implement service discovery based on specified files , Discover monitoring targets based on specified files 

dns_sd_configs：#DNS Service discovery monitoring objectives 

prometheus Static service discovery for static_configs&