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 upno data for a UP target #5380
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Mar 18, 2019
This comment has been minimized.
This comment has been minimized.
|
Maybe add the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lcgogo commentedMar 18, 2019
Proposal
Use case. Why is this important?
I can see one target in prometheus target website, however, I can not get anything of it from prometheus database.
“Nice to have” is not a good use case. :)
Bug Report
What did you do?
I have config a target in the prometheus.yml and the target website is UP. However, in console, there is no target information. The other tragets are OK except that one
What did you expect to see?
What did you see instead? Under which circumstances?
Environment
ubuntu 18.04 docker 18.09.0 latest prometheus image
System information:
root@aws-elkprom-01:/data/prometheus# uname -srm
Linux 4.15.0-1029-aws x86_64
insert output of
uname -srmherePrometheus version:
root@aws-elkprom-01:/data/prometheus# docker exec -it prometheus /bin/sh
/prometheus $ prometheus --version
prometheus, version 2.5.0 (branch: HEAD, revision: 67dc912)
build user: root@578ab108d0b9
build date: 20181106-11:40:44
go version: go1.11.1
insert output of
prometheus --versionhereAlertmanager version:
insert output of
alertmanager --versionhere (if relevant to the issue)Prometheus configuration file:
List of labeled statically configured targets for this job.