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

DNS SD : target doesn't appears in Prometheus #3925

Closed
Whiteire opened this Issue Mar 8, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@Whiteire
Copy link

Whiteire commented Mar 8, 2018

What did you do?
I configured a job with dns_sd_configs. When I use dig command with the domain name, I got some results :

$ dig my.domain

;; ANSWER SECTION:
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domainc. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX
my.domain. 600 IN A XXX.XXX.XXX.XXX

But when I put the same domain name in my job prometheus, I got no result in the prometheus interface. I'm not sure to understand well how it works.

What did you expect to see?
The targets should appear in Prometheus.

What did you see instead? Under which circumstances?
I can see my job but with no results.

Environment

  • System information:

$ uname -srm
Linux 2.6.32-642.13.1.el6.x86_64 x86_64

  • Prometheus version:
    prometheus-2.2.0

  • Prometheus configuration file:
    [...]
    - job_name: xxx
    dns_sd_configs:
    - names:
    - my.domain
    [...]

Thanks for your help.

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Mar 8, 2018

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.

@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.