Alert Manager source URL to point to TLS URL of Prometheus

[sunils...@gmail.com]

Hi, 

I have setup prometheus with TLS using Nginx in front of Prometheus as below path. 

Request --> nginx --> Prometheus . 

Now the challenge is , AlertManager is directly associated with PRometheus and when I access AlertManager , All the source links ate pointing to Prometheus directly . 

Can we configure alertmanager source URL to TLS URL of Prometheus  ? 

Thanks 

[Wesley Peng]

You can setup Nginx to proxy both Alertmanager and Prometheus itself on
different http port.

regards.

[Sagar]

Hi Wesley, 

Thanks for your quick response on this .

My AlertManage is running behind Nginx . 

But on the Alertmanager page, as shown in below pic, the source link is pointing to the direct URL of Prometheus (without nginx). 

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/427ffa62-06f1-9e59-d613-310ddcf1a32b%40pobox.com.

[Julien Pivotto]

Hello,

You can set the nginx url with the --web.external-url parameter of Prometheus.

To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CANegE50ksJZzyssaC52g0nuAR-ppCNCSZ%3DOpnU341hbQ01bYGg%40mail.gmail.com.

[Sagar]

Hi Julien, 

Thanks for this solution  , this method worked . 

Prometheus is still accessible through port 9090 . Can we stop this accessibility, so that it is accessible only through nginx . 

Thanks 

[Brian Candler]

As long as nginx is proxying to 127.0.0.1:9090, bind prometheus to localhost using  --web.listen-address="127.0.0.1:9090"