How does Harvest HTTP Service Discovery decide the number of endpoints? #4053
-
|
https://netapp.github.io/harvest/25.11/prometheus-exporter/#harvest-http-service-discovery-options How is the number of endpoints determined by the Harvest HTTP Service Discovery? Does the system automatically scale the number of endpoints based on metric volume? We would like to understand its benefits over Static Scrape Targets. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The number of endpoints returned by No scaling is done based on metric volume. The advantage of service discovery over static scrape targets is one of configuration. Using service discovery means you do not have to keep the |
Beta Was this translation helpful? Give feedback.
The number of endpoints returned by
/api/v1/sdwill match the number of pollers in yourharvest.ymlthat have been configured to use a Prometheus exporter.No scaling is done based on metric volume.
The advantage of service discovery over static scrape targets is one of configuration. Using service discovery means you do not have to keep the
harvest.ymlPrometheus ports in-sync with Prometheus'sstatic_configs.targets. There are multiple ways to keep those files in-sync, service discovery is one of them.