gxthrj edited a comment on issue #700:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/700#issuecomment-941896136


   @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"
   ```
   
   2. The Prometheus svc 
   
![image](https://user-images.githubusercontent.com/4413028/137064173-ab0e3700-26e0-4947-b586-401e37840c3d.png)
   
   3. Request to Prometheus-2 directly
   
![image](https://user-images.githubusercontent.com/4413028/137064273-1c329670-821d-492c-8305-4a7663c6576e.png)
   
   4. Request to Proemtheus-2 from APISIX 
   _[**The same result as request to Prometheus-2 directly, which is 
expected**]_
   
![image](https://user-images.githubusercontent.com/4413028/137064354-2f7fb5ec-dfb6-410b-b0ef-645fbbd719a5.png)
   
   5. 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.
   
   


-- 
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]


Reply via email to