LuChenjing commented on issue #700: URL: https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-952786407
> @LuChenjing I have sorted out your screenshots, the configuration worked as expected, maybe you got it wrong understanding？ > > 1. The configuration paragraph of `prometheus-2` in ApisixRoute resource > > ```yaml > - name: prometheus-2 > match: > paths: > - /monitor2/* > backend: > serviceName: prometheus-monitoring-2 > servicePort: 9090 > plugins: > - name: proxy-rewrite > enable: true > config: > regex_uri: > - "^/monitor2/(.*)" > - "/$1" > ``` > > 1. The Prometheus svc >  > 2. Request to Prometheus-2 directly >  > 3. Request to Proemtheus-2 from APISIX > _[**The same result as request to Prometheus-2 directly, which is expected**]_ >  > 4. But， Request to APISIX by `http://100.71.8.124:30005/api/v1/status/config` , I can not see the configure `/api/*` in `ApisixRoute` manifest yaml. So we can’t tell which upstream the request is sent to, and need you to provide the relevant routing configuration. Hi @gxthrj sorry for this late reply... For point No.5, I am trying to access prometheus2 by path `/monitor2/`, but the request will direct to `http://100.71.8.124:30005/api/v1/status/config` after accessing `http://100.71.8.124:30005/monitor2/` on Chrome browser, this is the problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
