Jintao Zhang

Results 618 comments of Jintao Zhang

Obviously, it can configure multiple plugins. You should be able to query its actual results by calling the Admin API in APISIX

As for your specific question, I think this requires more information

``` { "modifiedIndex": 153, "value": { "id": "7ed9320f", "name": "test_route-backend_c", "labels": { "managed-by": "apisix-ingress-controller" }, "create_time": 1660182821, "status": 1, "uris": [ "\/backend_docs" ], "desc": "Created by apisix-ingress-controller, DO NOT modify...

From the results of the above Admin API, it does not include the plugin, as you expect. In the situation you are currently experiencing, the client request is actually failing,...

you can refer to this one https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/tutorials/how-to-access-Apache-APISIX-Prometheus-Metrics-on-k8s.md

no, you should use Prometheus to fetch `/apisix/prometheus/metrics` And add Prometheus as DataSource in Grafana.

Are your alerts log-based rather than metrics-based? Sounds like this would bring some convenience, but so far I haven't seen other similar feedback.

These logs are some expected output, but it also means that you are currently facing some situation. 1. Same as 👆 you have some routes not created by APISIX Ingress...