vladimirpetr opened a new issue, #14033:
URL: https://github.com/apache/apisix/issues/14033

   ### Description
   
   We have just upgraded from 3.13 to 3.17 via the Helm chart (2.11.0 to 
2.16.1). All's well apart from the custom metrics - these do not get generated 
any longer.
   
   The resulting configuration in the config file seems correct (I would expect 
`enable_export_server` there, though):
   
   ```yaml
   plugin_attr:
     prometheus:
       export_addr:
         ip: 0.0.0.0
         port: 9091
       export_uri: /apisix/prometheus/metrics
       metric_prefix: apisix_
       metrics:
         bandwidth:
           extra_labels:
           - upstream_addr: $upstream_addr
         http_latency:
           extra_labels:
           - upstream_addr: $upstream_addr
         http_status:
           extra_labels:
           - upstream_addr: $upstream_addr
           - upstream_status: $upstream_status
   ```
   
   The prometheus plugin is enabled on all routes via a _GlobalRule_ as before:
   
   ```yaml
   spec:
     plugins:
       - name: prometheus
         enable: true
         config:
           prefer_name: true
   ```
   
   The routes get hit frequently but the above mentioned metrics do not get 
generated. I have been looking at it but so far could not determine the cause. 
I would appreciate any hint. Cheers!
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.17
   - Operating system (run `uname -a`): flatcar 4593.2.0 kernel 6.12.81-flatcar
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):  
openresty/1.29.2.4
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`): none
   - APISIX Dashboard version, if relevant: none
   - Plugin runner version, for issues related to plugin runners: none
   - 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