Re: [prometheus-users] 404 Error as prometheus adds a port 443 to my aws app runner domain
Thanks for the quick reply Stuart, here i am facing an error with app runner domain i.e my app runner service don't include any port in its URL its simply https://example.apprunner.com when m using it with prometheus i.e https://example.apprunner.com/actuator/prometheus , it taking a default port 443 at https://example.apprunner.com:443 and thus throwing a 404 error as that's not my actual URL ( https://example.apprunner.com/actuator/prometheus ) On Monday, 13 February 2023 at 17:46:39 UTC+5:30 Stuart Clark wrote: > On 13/02/2023 09:16, V P wrote: > > We want to scrape a https app runner domain without a port number and > > the Prometheus configuration is according to that. Is there a way to > > prevent the default port number for https(443) to get applied in the > > domain name of app runner when the Prometheus targets the https domain? > > > > As my domain https://app-runner.com/actuator/prometheus gets converted > to > > https://app-runner.com:443/actuator/prometheus in the targets and > > gives a 404 error due to the addition on port number in url. > > > > I changed the scheme to https, tried adding 443 port in target field > > of yml config file as well still getting the same error 404 > > I'm not quite sure what you are meaning by "without a port number"? All > connections are to a specific port. If you don't specify a port when > doing a web request it will default to 80 or 443 (depending on if it is > HTTP or HTTPS). > > -- > Stuart Clark > > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/204c5439-842e-4cd7-870c-794c4b87db54n%40googlegroups.com.
[prometheus-users] How to supply the certificates in prometheus docker
Is there a way to add security certificates in Prometheus config from docker so as to avoid the https port number to get added in my target domain so I wont be getting a *404 error* in Prometheus. my domain : *https://app-runner.com/actuator/prometheus* instance created : *https://app-runner.com:443/actuator/prometheus *as 443 gets added here I get 404 error and my state is DOWN -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/7cf15363-0069-436c-86d5-9579e470f380n%40googlegroups.com.
[prometheus-users] 404 Error as prometheus adds a port 443 to my aws app runner domain
We want to scrape a https app runner domain without a port number and the Prometheus configuration is according to that. Is there a way to prevent the default port number for https(443) to get applied in the domain name of app runner when the Prometheus targets the https domain? As my domain https://app-runner.com/actuator/prometheus gets converted to https://app-runner.com:443/actuator/prometheus in the targets and gives a 404 error due to the addition on port number in url. I changed the scheme to https, tried adding 443 port in target field of yml config file as well still getting the same error 404 -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/bc79294c-cf35-47fb-9365-fcf2729f6e92n%40googlegroups.com.
