Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAzure Virtual Machine Scrape Failed #4630
Comments
This comment has been minimized.
This comment has been minimized.
|
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
closed this
Sep 19, 2018
This comment has been minimized.
This comment has been minimized.
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. |
oscarkim007 commentedSep 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 -srmhereLinux 3.10.0-862.11.6.el7.x86_64 x86_64
Prometheus version:
insert output of
prometheus --versionhereprometheus, 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 --versionhere (if relevant to the issue)Prometheus configuration file: