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 upPrometheus unable to resolve DNS to send alert notifications #2912
Comments
drewandersen
changed the title
Prometheus unable to resolve DNS to send messages
Prometheus unable to resolve DNS to send alert notifications
Jul 11, 2017
This comment has been minimized.
This comment has been minimized.
|
This is also true when using |
This comment has been minimized.
This comment has been minimized.
|
Usage questions are best asked on https://groups.google.com/forum/#!forum/prometheus-users |
brian-brazil
closed this
Jul 14, 2017
This comment has been minimized.
This comment has been minimized.
|
So it's expected behavior for Prometheus to detect an Alertmanager instance but fail to send alert messages? |
This comment has been minimized.
This comment has been minimized.
snguyen-ith
commented
Sep 18, 2018
|
@drewandersen Did you ever resolve this issue? |
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. |
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.
drewandersen commentedJul 6, 2017
What did you do?
Created two virtual machines on my local box for development: one running Prometheus and one running Alertmanager. Purposely triggered an alert on Prometheus.
What did you expect to see?
The alert in Alertmanager.
What did you see instead? Under which circumstances?
No alert. Instead, the following error:
Environment
Docker or Virtualbox running Ubuntu 14.04.
System information:
Linux 4.8.0-56-generic x86_64
Prometheus version:
prometheus, version 1.7.1 (branch: master, revision: 3afb3ff)
build user: root@0aa1b7fc430d
build date: 20170612-11:44:05
go version: go1.8.3
Alertmanager version:
alertmanager, version 0.5.1 (branch: master, revision: 0ea1cac51e6a620ec09d053f0484b97932b5c902)
build user: root@fb407787b8bf
build date: 20161125-08:14:40
go version: go1.7.3
Additional Information
The
alertmanager_dnsin the above error message resolves to an alias for another DNS which contains the A record. Cancurlanddigthealertmanager_dnsfrom the box where Prometheus is running and receive the expected result. Can even use the Alertmanager API to trigger an alert from the box running Prometheus. The metricprometheus_notifications_alertmanagers_discoveredshows a consistent value of 1. If I launch Prometheus and specify the DNS that contains the actual A record, the behavior is as expected (alerts are sent from Prometheus to Alertmanager). Also ran a quick Go service on the same host where Prometheus is running to make a GET request toalertmanager_dns, and it succeeded.Essentially, the DNS is resolvable everywhere except where Prometheus attempts to send alerts to Alertmanager.