unsw-luopan opened a new issue, #12854:
URL: https://github.com/apache/apisix/issues/12854

   ### Current Behavior
   
   My config.yaml is:
     plugins:
       - prometheus
       - request-id
       - zipkin
       - cors
       - public-api
       - key-auth
       - limit-count
     plugin_attr:
       prometheus:
         enable_export_server: true
         export_uri: /apisix/prometheus/metrics
         metric_prefix: apisix_
         export_addr:
           ip: 0.0.0.0
           port: 9091
   
   And "curl http://127.0.0.1:9091/apisix/prometheus/metrics";  return many 
metrics, but "curl http://10.150.9.179(my host 
ip):9091/apisix/prometheus/metrics" return "curl: (7) Failed to connect to 
10.150.9.179 port 9091 after 0 ms: Couldn't connect to server".
   
   I checked port 9091, only 127.0.0.1 can be  reached.
   ss -tunl |grep 9091
   tcp    LISTEN     0      128     127.0.0.1:9091                   *:*
   
   ### Expected Behavior
   
   Prometheus config ip:0.0.0.0 and ss -tunl |grep 9091 should return 
   tcp    LISTEN     0      128     0.0.0.0:9091                   *:*
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   apache/apisix:3.14.1-debian   
   bitnamilegacy/etcd   3.5.11
   
   Just run offical demo and configure prometheus.
   
   ### Environment
   
   - APISIX version (run `apisix version`):
   - Operating system (run `uname -a`):
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


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