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

UP status incorrectly given to anything in 2.0-alpha.2 #2796

Closed
johrstrom opened this Issue Jun 1, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@johrstrom
Copy link

johrstrom commented Jun 1, 2017

What did you do?
Misconfigured Prometheus 2.0-aplha.2 such that it attempts to scrape a host does not exist. It was then marked as UP even though it should not have been.

What did you expect to see?
Items marked appropriately in the /status page (UP iff they're up and DOWN iff they're down)

What did you see instead? Under which circumstances?
Everything is marked as UP regardless of whether that's actually true or not. You can replicate easily by using a host name that isn't reachable. You can use the config below.

  • Prometheus version:

prometheus, version 2.0.0-alpha.2 (branch: HEAD, revision: ab0ce4a)
build user: jeff@localhost.localdomain
build date: 20170525-21:21:28
go version: go1.8

  • Prometheus configuration file:
scrape_configs:
- job_name: "up-test"
  static_configs:
  - targets: ['does.not.exist']

@brian-brazil brian-brazil added the dev-2.0 label Jun 6, 2017

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Jun 6, 2017

This was fixed.

@iofxl

This comment has been minimized.

Copy link

iofxl commented Jun 12, 2017

How to build dev 2.0 . I just build a 1.7 version.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 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 23, 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.