prometheus-node-exporter

问题 Given the following prometheus time series called requests : the vector query requests[3 seconds] is : and the rate of the vector query requests[3 seconds], rate(requests[3 sec]) (computed by the shown formula) is : My question is : what is sum(rate(requests[3 sec])) evaluated at seconds 5, 4 and 3 respectively is it 16.5, 6.5 and 1. Any idea? 回答1: You are misunderstanding the purpose of sum. It is not performing a sum over time but over the dimensions for your metric. In your example,

问题 Given the following prometheus time series called requests : the vector query requests[3 seconds] is : and the rate of the vector query requests[3 seconds], rate(requests[3 sec]) (computed by the shown formula) is : My question is : what is sum(rate(requests[3 sec])) evaluated at seconds 5, 4 and 3 respectively is it 16.5, 6.5 and 1. Any idea? 回答1: You are misunderstanding the purpose of sum. It is not performing a sum over time but over the dimensions for your metric. In your example,

问题 Given the following prometheus time series called requests : the vector query requests[3 seconds] is : and the rate of the vector query requests[3 seconds], rate(requests[3 sec]) (computed by the shown formula) is : My question is : what is sum(rate(requests[3 sec])) evaluated at seconds 5, 4 and 3 respectively is it 16.5, 6.5 and 1. Any idea? 回答1: You are misunderstanding the purpose of sum. It is not performing a sum over time but over the dimensions for your metric. In your example,

问题 I'm looking for a query to get the average uptime of the server on which prometheus runs over the last week. It should be about 15h/week, so about 8-10 %. I'm using Prometheus 2.5.0 with node_exporter on CentOS 7.6.1810. My most promising experiments would be: 1 - avg_over_time(up{job="prometheus"}[7d]) This is what I've found when looking for ways to get average uptimes, but it gives me exactly 1. (My guess is it ignores the times in which no scrapes happened?) 2 - sum_over_time(up{job=

问题 I'm looking for a query to get the average uptime of the server on which prometheus runs over the last week. It should be about 15h/week, so about 8-10 %. I'm using Prometheus 2.5.0 with node_exporter on CentOS 7.6.1810. My most promising experiments would be: 1 - avg_over_time(up{job="prometheus"}[7d]) This is what I've found when looking for ways to get average uptimes, but it gives me exactly 1. (My guess is it ignores the times in which no scrapes happened?) 2 - sum_over_time(up{job=

问题 The Prometheus node exporter does not have a simple way to disable all default metrics without passing 20 flags to the process. In the documentation it looks like there might be an easier way to fetch only the relevant metrics: Filtering enabled collectors ... For advanced use the node_exporter can be passed an optional list of collectors to filter metrics. The collect[] parameter may be used multiple times. In Prometheus configuration you can use this syntax under the scrape config. params:

问题 I've configured prometheus on Centos, version details are follows. prometheus-2.5.0.linux-386 I've added two targets on the prometheus.yml configuration file, all the servers node exporters are running. Config as follows, scrape_configs: - job_name: "node" scrape_interval: "15s" target_groups: - targets: ['192.168.x.x:9100','192.168.x.y:9100'] But in the prometheus UI Tragets only showing single node other is not showing. If I remove one node existing node is showing. How can I monitor

问题 I've configured prometheus on Centos, version details are follows. prometheus-2.5.0.linux-386 I've added two targets on the prometheus.yml configuration file, all the servers node exporters are running. Config as follows, scrape_configs: - job_name: "node" scrape_interval: "15s" target_groups: - targets: ['192.168.x.x:9100','192.168.x.y:9100'] But in the prometheus UI Tragets only showing single node other is not showing. If I remove one node existing node is showing. How can I monitor