I run it like that and It Works For Me™

Alertmanager options:

OPTIONS='--config.file=/etc/prometheus/alertmanager.yml 
--web.external-url=http://example.com/alertmanager'
(note: I am *not* using any other options, including --web.path-prefix)

Prometheus options:

OPTIONS='--config.file=/etc/prometheus/prometheus.yml 
--storage.tsdb.path=/var/lib/prometheus/data/ 
--storage.tsdb.wal-compression 
--web.external-url=http://example.com/prometheus'

Apache config:

ProxyPass /prometheus http://127.0.0.1:9090/prometheus
ProxyPassReverse /prometheus http://127.0.0.1:9090/prometheus
ProxyPass /alertmanager http://127.0.0.1:9093/alertmanager
ProxyPassReverse /alertmanager http://127.0.0.1:9093/alertmanager

I think your problem might be that you also have "ProxyPass /" which routes 
the whole lot somewhere. I seem to remember it was very difficult to "punch 
a hole" in proxying like this, without using mod_rewrite and [P] (proxy) 
RewriteRules.  Try removing it.

On Saturday, 22 October 2022 at 15:34:59 UTC+2 [email protected] wrote:

> Thanks,
> i am running no cluster.  
> Alertmanager and prometheus are on the same machine.
>
> i am somhow not able to make this work with apache and SSL
>
> best regards
> Philipp
>
> [email protected] schrieb am Samstag, 22. Oktober 2022 um 15:31:08 
> UTC+2:
>
>> I use the following jinja template to expose alertmanagers on 
>> `/alertmanager`
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *############################################################ 
>> Alertmanager###########################################################Header
>>  
>> add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" 
>> env=BALANCER_ROUTE_CHANGED<Proxy balancer://alertmgrcluster> {%- for member 
>> in members %} BalancerMember http://{{ member }}:{{ port }} route={{ 
>> loop.index }} timeout=5 {%- endfor %} ProxySet lbmethod=bybusyness ProxySet 
>> stickysession=ROUTEID</Proxy>ProxyPass /alertmanager 
>> balancer://alertmgrclusterProxyPassReverse /alertmanager 
>> balancer://alertmgrcluster*
>> On Saturday, October 22, 2022 at 2:54:41 PM UTC+2 [email protected] 
>> wrote:
>>
>>> Wow thanks for the fast response!
>>>
>>>
>>> It looks like his now:
>>> ProxyPass           / http://localhost:9090/
>>> ProxyPassReverse    / http://localhost:9090/
>>> ProxyPass           / http://localhost:9093/
>>> ProxyPassReverse    / http://localhost:9093/
>>>
>>> but does not work either.
>>>
>>> [email protected] schrieb am Samstag, 22. Oktober 2022 um 
>>> 14:48:04 UTC+2:
>>>
>>>> Get rid of the /alertmanager in the proxypass statements and you should 
>>>> be good. 
>>>>
>>>> Get Outlook for iOS <https://aka.ms/o0ukef>
>>>> ------------------------------
>>>> *From:* [email protected] <[email protected]> on 
>>>> behalf of [email protected] <[email protected]>
>>>> *Sent:* Saturday, October 22, 2022 8:46:12 AM
>>>> *To:* Prometheus Users <[email protected]>
>>>> *Subject:* [prometheus-users] Prometheus and Alertmanager behind 
>>>> Apache Proxy 
>>>>  
>>>> Hi, I have Prometheus and Alertmanager running behind an Apache Proxy.
>>>>
>>>> My problem is that i cannot make Alertmanager accessible through
>>>> "https://my.url.com/alertmanager";
>>>> With my current config i only get an 404 for that site.
>>>>
>>>> I start Alertmanager with following flags:
>>>>
>>>> ExecStart=/etc/alertmanager/alertmanager 
>>>> --config.file=/etc/alertmanager/alertmanager.yml 
>>>> --storage.path=/etc/alertmanager/data --cluster.listen-address= 
>>>> --web.config.file=/etc/prometheus/web.yml --web.external-url=
>>>> https://my.url.com/alertmanager --web.route-prefix=/alertmanager
>>>>
>>>> and my Proxy looks like this:
>>>> <VirtualHost *:443>
>>>> ...
>>>> ProxyPass           / http://localhost:9090/
>>>> ProxyPassReverse    / http://localhost:9090/
>>>> ProxyPass           /alertmanager http://localhost:9093/alertmanager/
>>>> ProxyPassReverse    /alertmanager http://localhost:9093/alertmanager/
>>>> </VirtualHost>
>>>>
>>>> please send some help!!!
>>>>
>>>> -- 
>>>> 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 [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/prometheus-users/98a2def6-78ee-41b4-a192-10ba117888bcn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/prometheus-users/98a2def6-78ee-41b4-a192-10ba117888bcn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/aebfcbd4-6e47-4f73-928c-446eacf52c18n%40googlegroups.com.

Reply via email to