init_config:instances:## @param kong_status_url - string - required## URL where Kong exposes its status.#- kong_status_url:http://localhost:8001/status/
Avec l’Agent 7+, il est également possible d’utiliser une implémentation plus moderne :
init_config:instances:## @param openmetrics_endpoint - string - required## The URL exposing metrics in the OpenMetrics format.#- openmetrics_endpoint:http://localhost:8001/metrics
Modifiez les valeurs des paramètres path et service et configurez-les pour votre environnement. Consultez le fichier d’exemple kong.d/conf.yaml pour découvrir toutes les options de configuration disponibles.
[OpenMetrics V2] The total bandwidth in bytes consumed per service/route in Kong Shown as byte
kong.http.consumer.status.count (count)
[OpenMetrics V2] HTTP status codes for customer per service/route in Kong Shown as request
kong.http.status.count (count)
[OpenMetrics V2] HTTP status codes per service/route in Kong Shown as request
kong.latency.bucket (count)
[OpenMetrics V2] The latency added by Kong, total request time and upstream latency for each service/route in Kong Shown as millisecond
kong.latency.count (count)
[OpenMetrics V2] The latency added by Kong, total request time and upstream latency for each service/route in Kong Shown as millisecond
kong.latency.sum (count)
[OpenMetrics V2] The latency added by Kong, total request time and upstream latency for each service/route in Kong Shown as millisecond
kong.memory.lua.shared_dict.bytes (gauge)
[OpenMetrics V2] The allocated slabs in bytes in a shared_dict Shown as byte
kong.memory.lua.shared_dict.total_bytes (gauge)
[OpenMetrics V2] The total capacity in bytes of a shared_dict Shown as byte
kong.memory.workers.lua.vms.bytes (gauge)
[OpenMetrics V2] The allocated bytes in worker Lua VM Shown as byte
kong.nginx.http.current_connections (gauge)
[OpenMetrics V2] The number of HTTP connections Shown as connection
kong.nginx.stream.current_connections (gauge)
[OpenMetrics V2] The number of stream connections Shown as connection
kong.stream.status.count (count)
[OpenMetrics V2] The stream status codes per service/route in Kong Shown as request
kong.table.count (gauge)
[Legacy]Total number of tables in the database. Shown as table
kong.table.items (gauge)
[Legacy] Number of items in each table of the database. Shown as row
kong.connections_accepted (gauge)
[Legacy] Total number of accepted client connections. Shown as connection
kong.connections_active (gauge)
[Legacy] Current number of active client connections including Waiting connections. Shown as connection
kong.connections_handled (gauge)
[Legacy] Total number of handled connections. (Same as accepts unless resource limits were reached). Shown as connection
kong.connections_reading (gauge)
[Legacy] Current number of connections where Kong is reading the request header. Shown as connection
kong.connections_waiting (gauge)
[Legacy] Current number of idle client connections waiting for a request. Shown as connection
kong.connections_writing (gauge)
[Legacy] Current number of connections where nginx is writing the response back to the client. Shown as connection
kong.total_requests (gauge)
[Legacy] Total number of client requests. Shown as request
Événements
Le check Kong n’inclut aucun événement.
Checks de service
kong.can_connect : Renvoie CRITICAL si l’Agent ne parvient pas à se connecter à Kong pour recueillir des métriques. Si ce n’est pas le cas, renvoie OK.
Lorsque vous utilisez l’implémentation de l’Agent 7+ en définissant openmetrics_endpoint :
kong.openmetrics.health : Renvoie CRITICAL si l’Agent ne parvient pas à se connecter à l’endpoint OpenMetrics. Si ce n’est pas le cas, renvoie OK.
kong.datastore.reachable : Renvoie CRITICAL si Kong ne parvient pas à se connecter au datastore. Si ce n’est pas le cas, renvoie OK.
kong.upstream.target.health : Renvoie CRITICAL lorsque la cible n’est pas saine. Si ce n’est pas le cas, renvoie OK.