Skip to main content
Version: 2.5

prometheus

This plugin exposes metrics in Prometheus Exposition format.

Attributes#

none.

API#

This plugin will add /apisix/prometheus/metrics to expose the metrics. You may need to use interceptors to protect it.

How to enable it#

prometheus plugin can be enable with empty table, because it doesn't have any options yet.

For example:

curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"uri": "/hello",
"plugins": {
"prometheus":{}
},
"upstream": {
"type": "roundrobin",
"nodes": {
"127.0.0.1:80": 1
}
}
}'

You can open dashboard with a browser: http://127.0.0.1:9080/apisix/dashboard/, to complete the above operation through the web interface, first add a route:

Then add prometheus plugin:

How to fetch the metric data#

We fetch the metric data from the specified url /apisix/prometheus/metrics.

curl -i http://127.0.0.1:9080/apisix/prometheus/metrics

Puts this URL address into prometheus, and it will automatically fetch these metric data.

For example like this:

scrape_configs:
- job_name: 'apisix'
metrics_path: '/apisix/prometheus/metrics'
static_configs:
- targets: ['127.0.0.1:9080']

And we can check the status at prometheus console:

How to specify export uri#

We can change the default export uri in the plugin_attr section of conf/config.yaml.

NameTypeDefaultDescription
export_uristring"/apisix/prometheus/metrics"uri to get the prometheus metrics

Here is an example:

plugin_attr:
prometheus:
export_uri: /apisix/metrics

Grafana dashboard#

Metrics exported by the plugin can be graphed in Grafana using a drop in dashboard.

Downloads Grafana dashboard meta and imports it to Grafana。

Or you can goto Grafana official for Grafana meta data.

Available metrics#

  • Status codes: HTTP status code returned from upstream services. These status code available per service and across all services.

    Attributes:

    NameDescription
    codeThe HTTP status code returned by the upstream service.
    routeThe route_id of the matched route is request. If it does not match, the default value is an empty string.
    matched_uriThe uri of the route matching the request, if it does not match, the default value is an empty string.
    matched_hostThe host of the route that matches the request. If it does not match, the default value is an empty string.
    serviceThe service_id of the route matched by the request. When the route lacks service_id, the default is $host.
    consumerThe consumer_name of the consumer that matches the request. If it does not match, the default value is an empty string.
    nodeThe ip of the upstream node.
  • Bandwidth: Total Bandwidth (egress/ingress) flowing through APISIX. The total bandwidth of per service can be counted.

    Attributes:

    NameDescription
    typeThe type of bandwidth(egress/ingress).
    routeThe route_id of the matched route is request. If it does not match, the default value is an empty string..
    serviceThe service_id of the route matched by the request. When the route lacks service_id, the default is $host.
    consumerThe consumer_name of the consumer that matches the request. If it does not match, the default value is an empty string.
    nodeThe ip of the upstream node.
  • etcd reachability: A gauge type with a value of 0 or 1, representing if etcd can be reached by a APISIX or not, where 1 is available, and 0 is unavailable.

  • Connections: Various Nginx connection metrics like active, reading, writing, and number of accepted connections.

  • Batch process entries: A gauge type, when we use plugins and the plugin used batch process to send data, such as: sys logger, http logger, sls logger, tcp logger, udp logger and zipkin, then the entries which hasn't been sent in batch process will be counted in the metrics.

  • Latency: The per service histogram of request time and the overhead added by APISIX (request time - upstream response time).

    Attributes:

    NameDescription
    typeIts value is fixed as request, which means HTTP request.
    serviceThe service_id of the route matched by the request. When the route lacks service_id, the default is $host.
    consumerThe consumer_name of the consumer that matches the request. If it does not match, the default value is an empty string.
    nodeThe ip of the upstream node.
  • Overhead: HTTP request overhead (in milliseconds) added per service in APISIX.

    Attributes: | Name | Description | | ---------| ------------- | | type | Its value is fixed as request, which means HTTP request. | | service | The service_id of the route matched by the request. When the route lacks service_id, the default is $host. | | consumer | The consumer_name of the consumer that matches the request. If it does not match, the default value is an empty string. | | node | The ip of the upstream node. |

  • Info: the information of APISIX node.

Here is the original metric data of APISIX:

$ curl http://127.0.0.1:9080/apisix/prometheus/metrics
# HELP apisix_bandwidth Total bandwidth in bytes consumed per service in Apisix
# TYPE apisix_bandwidth counter
apisix_bandwidth{type="egress",route="",service="127.0.0.1",consumer="",node=""} 8417
apisix_bandwidth{type="egress",route="1",service="",consumer="",node="127.0.0.1"} 1420
apisix_bandwidth{type="egress",route="2",service="",consumer="",node="127.0.0.1"} 1420
apisix_bandwidth{type="ingress",route="",service="127.0.0.1",consumer="",node=""} 189
apisix_bandwidth{type="ingress",route="1",service="",consumer="",node="127.0.0.1"} 332
apisix_bandwidth{type="ingress",route="2",service="",consumer="",node="127.0.0.1"} 332
# HELP apisix_etcd_modify_indexes Etcd modify index for APISIX keys
# TYPE apisix_etcd_modify_indexes gauge
apisix_etcd_modify_indexes{key="consumers"} 0
apisix_etcd_modify_indexes{key="global_rules"} 0
apisix_etcd_modify_indexes{key="max_modify_index"} 222
apisix_etcd_modify_indexes{key="prev_index"} 35
apisix_etcd_modify_indexes{key="protos"} 0
apisix_etcd_modify_indexes{key="routes"} 222
apisix_etcd_modify_indexes{key="services"} 0
apisix_etcd_modify_indexes{key="ssls"} 0
apisix_etcd_modify_indexes{key="stream_routes"} 0
apisix_etcd_modify_indexes{key="upstreams"} 0
apisix_etcd_modify_indexes{key="x_etcd_index"} 223
# HELP apisix_batch_process_entries batch process remaining entries
# TYPE apisix_batch_process_entries gauge
apisix_batch_process_entries{name="http-logger",route_id="9",server_addr="127.0.0.1"} 1
apisix_batch_process_entries{name="sls-logger",route_id="9",server_addr="127.0.0.1"} 1
apisix_batch_process_entries{name="tcp-logger",route_id="9",server_addr="127.0.0.1"} 1
apisix_batch_process_entries{name="udp-logger",route_id="9",server_addr="127.0.0.1"} 1
apisix_batch_process_entries{name="sys-logger",route_id="9",server_addr="127.0.0.1"} 1
apisix_batch_process_entries{name="zipkin_report",route_id="9",server_addr="127.0.0.1"} 1
# HELP apisix_etcd_reachable Config server etcd reachable from Apisix, 0 is unreachable
# TYPE apisix_etcd_reachable gauge
apisix_etcd_reachable 1
# HELP apisix_http_status HTTP status codes per service in Apisix
# TYPE apisix_http_status counter
apisix_http_status{code="200",route="1",matched_uri="/hello",matched_host="",service="127.0.0.2",consumer="",node="127.0.0.1"} 4
apisix_http_status{code="200",route="2",matched_uri="/world",matched_host="",service="bar.com",consumer="",node="127.0.0.1"} 4
apisix_http_status{code="404",route="",matched_uri="",matched_host="",service="127.0.0.1",consumer="",node=""} 1
# HELP apisix_nginx_http_current_connections Number of HTTP connections
# TYPE apisix_nginx_http_current_connections gauge
apisix_nginx_http_current_connections{state="accepted"} 11994
apisix_nginx_http_current_connections{state="active"} 2
apisix_nginx_http_current_connections{state="handled"} 11994
apisix_nginx_http_current_connections{state="reading"} 0
apisix_nginx_http_current_connections{state="total"} 1191780
apisix_nginx_http_current_connections{state="waiting"} 1
apisix_nginx_http_current_connections{state="writing"} 1
# HELP apisix_nginx_metric_errors_total Number of nginx-lua-prometheus errors
# TYPE apisix_nginx_metric_errors_total counter
apisix_nginx_metric_errors_total 0
# HELP apisix_http_latency HTTP request latency in milliseconds per service in APISIX
# TYPE apisix_http_latency histogram
apisix_http_latency_bucket{type="request",service="",consumer="",node="127.0.0.1",le="1"} 1
apisix_http_latency_bucket{type="request",service="",consumer="",node="127.0.0.1",le="2"} 1
...
# HELP apisix_http_overhead HTTP request overhead added by APISIX in milliseconds per service in APISIX
# TYPE apisix_http_overhead histogram
apisix_http_overhead_bucket{type="request",service="",consumer="",node="127.0.0.1",le="1"} 1
apisix_http_overhead_bucket{type="request",service="",consumer="",node="127.0.0.1",le="2"} 1
...
# HELP apisix_node_info Info of APISIX node
# TYPE apisix_node_info gauge
apisix_node_info{hostname="desktop-2022q8f-wsl"} 1

Disable Plugin#

Remove the corresponding json configuration in the plugin configuration to disable prometheus. APISIX plugins are hot-reloaded, therefore no need to restart APISIX.

curl http://127.0.0.1:9080/apisix/admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
{
"uri": "/hello",
"plugins": {},
"upstream": {
"type": "roundrobin",
"nodes": {
"127.0.0.1:80": 1
}
}
}'