Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Virtual Machine Scrape Failed #4630

Closed
oscarkim007 opened this Issue Sep 19, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@oscarkim007
Copy link

oscarkim007 commented Sep 19, 2018

Proposal

Use case. Why is this important?

Nice to have' is not a good use case :)

Bug Report

What did you do?
I have setup prometheus 2.4.0 on Azure.
I want to monitoring Azure vm with Prometheus.

What did you expect to see?

What did you see instead? Under which circumstances?

Environment
Linux 3.10.0-862.11.6.el7.x86_64 x86_64

  • System information:

    insert output of uname -srm here
    Linux 3.10.0-862.11.6.el7.x86_64 x86_64

  • Prometheus version:

    insert output of prometheus --version here
    prometheus, version 2.4.0 (branch: HEAD, revision: 068eaa5)
    build user: root@d84c15ea5e93
    build date: 20180911-10:46:37
    go version: go1.10.3

  • Alertmanager version:
    None
    insert output of alertmanager --version here (if relevant to the issue)

  • Prometheus configuration file:

global:
  scrape_interval: 60s
  scrape_timeout: 60s
  #evaluation_interval: 5s
alerting:
  alertmanagers:
  - static_configs:
    - targets: []
    scheme: http
    timeout: 10s

scrape_configs:
- job_name: prometheus
  #scrape_interval: 15s
  #scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9090
- job_name: node_exporter
  #scrape_interval: 15s
  #scrape_timeout: 10s
  metrics_path: /metrics
  scheme: http
  static_configs:
  - targets:
    - localhost:9100
- job_name: Azure Production
  #tls_config:
  #  insecure_skip_verify: true
  #scrape_interval: 15s
  #scrape_timeout: 60s
  metrics_path: /metrics
  scheme: http
  azure_sd_configs:
  - environment: AzurePublicCloud
    #port: 80
    port: 9100
    subscription_id: c66aeac0-xxxx
    tenant_id: 539266e1-xxxx
    client_id: e4580130-xxxx
    client_secret: c63fafbc-xxxx
    refresh_interval: 1m
  • Alertmanager configuration file:
insert configuration here (if relevant to the issue)
  • Logs:
Sep 19 06:03:10 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:03:10.640009927Z caller=manager.go:183 component="discovery manager scrape" msg="discoverer exited" provider=string/1
Sep 19 06:03:10 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:03:10.929572281Z caller=azure.go:257 component="discovery manager scrape" discovery=azure msg="Found virtual machines during Azure discovery." count=2
Sep 19 06:03:11 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:03:11.087499492Z caller=azure.go:358 component="discovery manager scrape" discovery=azure msg="Azure discovery completed"
Sep 19 06:04:10 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:04:10.914587558Z caller=azure.go:257 component="discovery manager scrape" discovery=azure msg="Found virtual machines during Azure discovery." count=2
Sep 19 06:04:11 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:04:11.08521695Z caller=azure.go:358 component="discovery manager scrape" discovery=azure msg="Azure discovery completed"
Sep 19 06:04:28 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:04:28.275407988Z caller=scrape.go:794 component="scrape manager" scrape_pool="Azure Production" target=http://10.0.0.4:9100/metrics msg="Scrape failed" err="context deadline exceeded"
Sep 19 06:04:49 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:04:49.114757386Z caller=scrape.go:794 component="scrape manager" scrape_pool="Azure Production" target=http://10.0.0.5:9100/metrics msg="Scrape failed" err="context deadline exceeded"
Sep 19 06:05:11 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:05:11.045869272Z caller=azure.go:257 component="discovery manager scrape" discovery=azure msg="Found virtual machines during Azure discovery." count=2
Sep 19 06:05:11 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:05:11.148141326Z caller=azure.go:358 component="discovery manager scrape" discovery=azure msg="Azure discovery completed"
Sep 19 06:05:28 srv-prometheus prometheus[7339]: level=debug ts=2018-09-19T06:05:28.275740064Z caller=scrape.go:794 component="scrape manager" scrape_pool="Azure Production" target=http://10.0.0.4:9100/metrics msg="Scrape failed" err="context deadline exceeded"
@gouthamve

This comment has been minimized.

Copy link
Member

gouthamve commented Sep 19, 2018

Hi, this looks more like a configuration issue rather than a bug.

To make your question, and all replies, easier to find, we suggest you move this over to our user mailing list, which you can also search. If you prefer more interactive help, join or our IRC channel, #prometheus on irc.freenode.net. Please be aware that our IRC channel has no logs, is not searchable, and that people might not answer quickly if they are busy or asleep. If in doubt, you should choose the mailing list.

Once your questions have been answered, please add a short line pointing to relevant replies in case anyone stumbles here via a search engine in the future.

@gouthamve gouthamve closed this Sep 19, 2018

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 22, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.