-
Notifications
You must be signed in to change notification settings - Fork 58
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
What is the correct URL to configure #47
Comments
I have the same issue. |
i should work with the 2nd option (http://localhost:9093) usually the error HTTP Error Bad Gateway is when:
please close this issue. |
Please don't close this issue, it's a real bug. My alertmanager is up, running on localhost and on the port 9093 |
@craph According to your comments, I assume that you have, in your environment, a Prometheus server which is listening on 127.0.0.1:9090, an Alertmanager listening on 127.0.0.1:9093 and a Grafana server. Are you able to manually reach the status endpoint? Like by doing: $ curl -v -X GET http://localhost:9093/api/v1/status |
How does the release of alert manager 0.16 affect this plugin now the v2 of the API has been released ? |
@VR6Pete For now, the v1 is only deprecated so the datasource should work as excepted with the Alertmanager 0.16. Adding support of the API v2 is planned for the next weeks. |
Great, I will update alert manager in that case. |
Hello,
I am unable to configure the plugin in Grafana.
What is the correct url to configure ? is it
http://localhost:9090
orhttp://localhost:9093
With the first URL (URL for Prometheus) I have :
With the second URL :
Thank you for your help
Best regards
The text was updated successfully, but these errors were encountered: