Sindweller opened a new issue #691:
URL: https://github.com/apache/apisix-ingress-controller/issues/691
### Issue description
I'm working on editing the Grafana Dashboard for apisix-ingress-controller,
and I have some questions:
- I try to increase some metric counters by specify operations. There's
still no data in metric `apisix_ingress_controller_events_total` (Number of
events handled by the controller), and
`apisix_ingress_controller_check_cluster_health_total`(Number of cluster health
check operations), what actually should I do to increase them?
- We have many counters in metrics, such as `events_total` (Number of events
handled by the controller), should I set them
`irate(apisix_ingress_controller_events_total[2m])` to show a status or just
show `apisix_ingress_controller_events_total` as a graph?
- I currently understand it as we edit crd yaml and `kubectl apply -f` them
to complete the operations of route, upstream and so on through
apisix-ingress-controller, so any of these operations will increase the
counter, is it correct?
---
Here are the metrics:
```
# HELP apisix_ingress_controller_apisix_request_latencies Request latencies
with APISIX
# TYPE apisix_ingress_controller_apisix_request_latencies summary
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="create"}
3.4001866e+07
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="create"}
2
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="get"}
2.2852734e+07
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="get"}
6
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="getList"}
2.358962e+06
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="getList"}
1
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="getSchema"}
6.8506066e+07
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="getSchema"}
41
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="list"}
2.3190828e+07
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="list"}
6
apisix_ingress_controller_apisix_request_latencies_sum{controller_namespace="default",controller_pod="",operation="update"}
8.874494e+06
apisix_ingress_controller_apisix_request_latencies_count{controller_namespace="default",controller_pod="",operation="update"}
1
# HELP apisix_ingress_controller_apisix_requests Number of requests to APISIX
# TYPE apisix_ingress_controller_apisix_requests counter
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="consumer"}
1
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="globalRule"}
1
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="route"}
2
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="ssl"}
1
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="streamRoute"}
1
apisix_ingress_controller_apisix_requests{controller_namespace="default",controller_pod="",resource="upstream"}
3
# HELP apisix_ingress_controller_apisix_status_codes Status codes of
requests to APISIX
# TYPE apisix_ingress_controller_apisix_status_codes gauge
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="consumer",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="globalRule",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="plugin",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="route",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="route",status_code="201"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="schema",status_code="200"}
41
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="ssl",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="streamRoute",status_code="200"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="upstream",status_code="200"}
2
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="upstream",status_code="201"}
1
apisix_ingress_controller_apisix_status_codes{controller_namespace="default",controller_pod="",resource="upstream",status_code="404"}
6
# HELP apisix_ingress_controller_cache_sync_total Number of cache sync
operations
# TYPE apisix_ingress_controller_cache_sync_total counter
apisix_ingress_controller_cache_sync_total{controller_namespace="default",controller_pod="",result="success"}
1
# HELP apisix_ingress_controller_is_leader Whether the role of controller
instance is leader
# TYPE apisix_ingress_controller_is_leader gauge
apisix_ingress_controller_is_leader{controller_namespace="default",controller_pod=""}
0
# HELP apisix_ingress_controller_sync_operation_total Number of sync
operations
# TYPE apisix_ingress_controller_sync_operation_total counter
apisix_ingress_controller_sync_operation_total{controller_namespace="default",controller_pod="",resource="schema",result="success"}
1
```
And here the grafana dashboard looks like (if needed):
--
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]
