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"
--
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,
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
On Mon, Sep 14, 2020 at 2:21 PM Julien Pivotto
wrote:
> Hello,
>
> You can set the nginx url with
Hello,
You can set the nginx url with the --web.external-url parameter of
Prometheus.
Le lun. 14 sept. 2020 à 08:03, Sagar a écrit :
> 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
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).
[image: image.png]
On Mon, Sep 14, 2020 at 1:50 PM Wesley Peng wrote:
You can setup Nginx to proxy both Alertmanager and Prometheus itself on
different http port.
regards.
sunils...@gmail.com wrote:
Now the challenge is , AlertManager is directly associated with
PRometheus and when I access AlertManager , All the source links ate
pointing to Prometheus
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 .
6 matches
Mail list logo
