Prometheus

How to configure a specific IP in prometheus yml configuration file?

╄→гoц情女王★ 提交于 2020-06-01 06:36:29
问题 I would like to run Prometheus with a specific IP address. By default, it is running on localhost. I don't see any such option in the prometheus configuration 回答1: You can use the command line option for configuring your listen address ./prometheus --web.listen-address="0.0.0.0:9090" 回答2: If you're using the packages for Debian-based systems, you can persistently modify the command line argument --web.listen-address in /etc/default/prometheus (and same for /etc/default/prometheus-node

Context Deadline Exceeded - prometheus

北慕城南 提交于 2020-05-25 12:06:14
问题 I have prometheus configuration with many jobs where i am scraping metrics over http. But I have one job where i need to scrape the metrics over https. When i access: https://ip-address:port/metrics I can see the metrics. The job that I have added in the prometheus.yml configuration is: - job_name: 'test-jvm-metrics' scheme: https static_configs: - targets: ['ip:port'] When i restart the prometheus I can see error on my target that says: context deadline exceeded I have read that maybe the

Context Deadline Exceeded - prometheus

a 夏天 提交于 2020-05-25 12:06:09
问题 I have prometheus configuration with many jobs where i am scraping metrics over http. But I have one job where i need to scrape the metrics over https. When i access: https://ip-address:port/metrics I can see the metrics. The job that I have added in the prometheus.yml configuration is: - job_name: 'test-jvm-metrics' scheme: https static_configs: - targets: ['ip:port'] When i restart the prometheus I can see error on my target that says: context deadline exceeded I have read that maybe the

How to trigger alert in Kubernetes using Prometheus Alert Manager

好久不见. 提交于 2020-05-16 20:11:51
问题 I have setup kube-prometheus in my cluster(https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus). It contains some default alerts like "CoreDNSdown etc". How to create my own alert? Could any one provide me sample example to create an alert that will send an email to my gmail account? I followed this Alert when docker container pod is in Error or CarshLoopBackOff kubernetes. But I couldn't make it work. 回答1: To send an alert to your gmail account, you need to

How to trigger alert in Kubernetes using Prometheus Alert Manager

南楼画角 提交于 2020-05-16 20:11:29
问题 I have setup kube-prometheus in my cluster(https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus). It contains some default alerts like "CoreDNSdown etc". How to create my own alert? Could any one provide me sample example to create an alert that will send an email to my gmail account? I followed this Alert when docker container pod is in Error or CarshLoopBackOff kubernetes. But I couldn't make it work. 回答1: To send an alert to your gmail account, you need to

How to trigger alert in Kubernetes using Prometheus Alert Manager

扶醉桌前 提交于 2020-05-16 20:11:28
问题 I have setup kube-prometheus in my cluster(https://github.com/coreos/prometheus-operator/tree/master/contrib/kube-prometheus). It contains some default alerts like "CoreDNSdown etc". How to create my own alert? Could any one provide me sample example to create an alert that will send an email to my gmail account? I followed this Alert when docker container pod is in Error or CarshLoopBackOff kubernetes. But I couldn't make it work. 回答1: To send an alert to your gmail account, you need to

Actuator /metrics endpoint does not include http.server.requests

牧云@^-^@ 提交于 2020-05-16 05:39:48
问题 According to the documentation of the spring boot actuator Auto-configuration enables the instrumentation of requests handled by Spring MVC. When management.metrics.web.server.auto-time-requests is true, this instrumentation occurs for all requests. Alternatively, when set to false, you can enable instrumentation by adding @Timed And By default, metrics are generated with the name, http.server.requests When I access the /metrics endpoint I am getting { "mem": 405105, "mem.free": 150352,

Prometheus (in Docker container) Cannot Scrape Target on Host

戏子无情 提交于 2020-05-12 23:28:43
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get

Prometheus (in Docker container) Cannot Scrape Target on Host

我的未来我决定 提交于 2020-05-12 23:28:39
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get

Prometheus (in Docker container) Cannot Scrape Target on Host

安稳与你 提交于 2020-05-12 23:26:58
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get