Widely inspired by nginx-lua-prometheus NGINX module and the Kong StatsD plugin.
Exposes API metrics for Prometheus monitoring system.
Install the luarocks utility on your system then install it by doing:
$ luarocks install kong-plugin-prometheusConfiguring the plugin is straightforward, you can add it on top of an API by executing the following request on your Kong server:
$ curl -X POST http://kong:8001/apis/{api}/plugins \
--data "name=prometheus"api: The id or name of the API that this plugin configuration will target
You can also apply it for every API using the http://kong:8001/plugins/
endpoint.
| parameter | default | description |
|---|---|---|
name |
The name of the plugin to use, in this case: prometheus |
|
config.metricsoptional |
All metrics are logged |
List of Metrics to be logged. Available values are described under Metrics. |
config.dict_nameoptional |
kong_cache |
The name of the nginx shared dictionary which will be used to store all metrics. |
config.prefixoptional |
kong |
String to be prefixed to each metric's name. |
If you use a custom shared dictionary to store the metrics, you need to create a kong configuration template including the shared dictionary:
lua_shared_dict prometheus_metrics 10M;
The plugin exposes is metrics on kong's admin endpoint (port 8001 by default) on the path /prometheus/metrics.
Metrics the plugin can expose in the prometheus format:
| Metric | description | namespace |
|---|---|---|
http_requests_total |
tracks api request | kong_http_requests_total |
http_request_size_bytes |
tracks api request's body size in bytes | kong_http_request_size_bytes |
http_response_size_bytes |
tracks api response's body size in bytes | kong_http_response_size_bytes |
http_request_duration_ms |
tracks the time interval between the request started and response received from the upstream server | kong_http_latency |
http_upstream_duration_ms |
tracks the time it took for the final service to process the request | kong_http_upstream_latency |
http_kong_duration_ms |
tracks the internal Kong latency that it took to run all the plugins | kong_http_kong_latency |
Plugin can be configured with any combination of Metrics, with each entry containing the following fields.
| Field | description | allowed values |
|---|---|---|
name |
Prometheus metric's name | Metrics |
stat_type |
determines what sort of event the metric represents | gauge, counter and histogram |
This logging plugin will only log HTTP request and response data. If you are looking for the Kong process error file (which is the nginx error file), then you can find it at the following path: prefix/logs/error.log
The module increments the kong_metric_errors_total metric if it encounters an error (for example, when lua_shared_dict becomes full). You might want to configure an alert on that metric.
Please keep in mind that all metrics stored by this library are kept in a
single shared dictionary (lua_shared_dict). By default, we use the kong_cache shared dict so if you are using it remember to allow extra space to it.
While exposing metrics the module has to list all dictionary keys, which has serious performance implications for
dictionaries with large number of keys (in this case this means large number
of metrics OR metrics with high label cardinality). Listing the keys has to
lock the dictionary, which blocks all threads that try to access it (i.e.
potentially all nginx worker threads).
There is no elegant solution to this issue (besides keeping metrics in a separate storage system external to nginx), so for latency-critical servers you might want to keep the number of metrics (and distinct metric label values) to a minimum.
All prometheus implementation credits goes to nginx-lua-prometheus
- Created and maintained by Anton Tolchanov (@knyar)
- Metrix prefix support contributed by david birdsong (@davidbirdsong)
- Gauge support contributed by Cosmo Petrich (@cosmopetrich)
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent