Skip to main content
Version: Next

Monitoring APISIX with Helm Chart

APISIX has detailed telemetry data. With helm chart, we can easily configure the monitoring system.

This tutorial will show how to achieve it.

Install Prometheus and Grafana#

To collect metrics and visualize them, we need to install Prometheus and Grafana first.

The APISIX helm chart we will deploy later also contains a ServiceMonitor resource, so we should ensure the cluster has its CRD installed. Installing Prometheus Operator will apply the required CRD.

Run the following command to install Prometheus Operator and Grafana:

helm repo add prometheus-community
helm repo update

helm install -n monitoring prometheus prometheus-community/kube-prometheus-stack \
--create-namespace \
--set 'prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues=false'

We set option prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues to false to force Prometheus to watch all service monitors in the cluster for test purposes.

The default Grafana username and password is admin and prom-operator.

Install APISIX#

We should enable service monitor to tell Prometheus to collect metrics from APISIX.

Install APISIX via helm chart with serviceMonitor.enabled=true option:

helm repo add apisix
helm repo update

helm install apisix apisix/apisix --create-namespace --namespace apisix \
--set ingress-controller.config.apisix.serviceNamespace=apisix \
--set serviceMonitor.enabled=true \
--set ingress-controller.enabled=true

Configure Grafana Dashboard#

Import APISIX Grafana dashboard via dashboard ID 11719.

The dashboard should be able to display some data, including total requests, handled connections, etc. Routing-related panels such as bandwidth and latency will show "No data" because we haven't made any requests yet. Create some routes with the "prometheus" plugin enabled and make some requests to them to generate some data for these panels.

Manual Configuration and Troubleshooting#

If you already have an installation of APISIX and Prometheus Operator, you can manually configure the ServiceMonitor resource and the service that exposes APISIX metrics.

Service Monitor and APISIX Service#

The magic behind serviceMonitor.enabled=true helm chart option is ServiceMonitor resource. Its content is as follows.

kind: ServiceMonitor
- apisix
matchLabels: apisix-1.1.1 apisix apisix "3.1.1" Helm apisix-gateway
- scheme: http
targetPort: prometheus
path: /apisix/prometheus/metrics
interval: 15s

The spec uses namespaceSelector and selector to match the apisix-gateway service. The former matches the namespace of APISIX we deployed, and the latter matches the exact service apisix-gateway.

The field endpoints tells Prometheus where to collect the metrics. Note that the targetPort field points to the port of service with the same name. If your service doesn't have a port named prometheus, create one.

The helm chart exposes APISIX metrics in the apisix-gateway service by default. Change the selector to match your service if needed.

Prometheus Spec#

If everything works fine, the Status > Targets page of Prometheus Web UI will show the APISIX service monitor. If you don't see it, you should make sure Prometheus is watching the ServiceMonitor resource we created.

By default, the Prometheus resource created by the helm chart kube-prometheus-stack is as follows.

kind: Prometheus
serviceMonitorNamespaceSelector: {}
release: prometheus

Thus, we pass the option prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues=false to clear the serviceMonitorSelector field. Configure this resource to fit your needs.

For example, if you want to set service monitor selector to prom=watching, your helm command should be:

helm install -n monitoring prometheus prometheus-community/kube-prometheus-stack \
--create-namespace \
--set 'prometheus.prometheusSpec.serviceMonitorSelector.matchLabels.prom=watching'

Because we set values for serviceMonitorSelector, so we don't need to configure serviceMonitorSelectorNilUsesHelmValues anymore.