Prometheus /metrics info

1

hi,

i am using kong 2.0.3 db-less version in kubernetes. i have configured prometheus plugin for monitoring it.

  1. HELP kong_datastore_reachable Datastore reachable from Kong, 0 is unreachable

TYPE kong_datastore_reachable gauge

kong_datastore_reachable 1

kong_memory_lua_shared_dict_bytes{shared_dict=“kong_core_db_cache”} 831488
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_core_db_cache_2”} 794624
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_core_db_cache_miss”} 86016
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_core_db_cache_miss_2”} 86016
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_db_cache”} 794624
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_db_cache_2”} 794624
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_db_cache_miss”} 86016
kong_memory_lua_shared_dict_bytes{shared_dict=“kong_db_cache_miss_2”} 86016

kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_core_db_cache”} 134217728
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_core_db_cache_2”} 134217728
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_core_db_cache_miss”} 12582912
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_core_db_cache_miss_2”} 12582912
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_db_cache”} 134217728
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_db_cache_2”} 134217728
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_db_cache_miss”} 12582912
kong_memory_lua_shared_dict_total_bytes{shared_dict=“kong_db_cache_miss_2”} 12582912

[why it is giving db reachability is 1 and other db related metrics when i am using db-less mode of kong]

can we update plugin metrics to not show these metrics for db-less mode?

Thanks & Regards,

2

This is an oversight on our end. Can you please open an issue in the plugin repository?

3

Thanks for your reply,

i will open and i have found one more issue now,

i could not able to get below /metrics from my kong with prometheus plugin enabled.

kong_http_status{code=“301”,service=“google”} 2

HELP kong_latency Latency added by Kong, total request time and upstream latency for each service in Kong

TYPE kong_latency histogram

kong_latency_bucket{type=“kong”,service=“google”,le=“00001.0”} 1
kong_latency_bucket{type=“kong”,service=“google”,le=“00002.0”} 1
.
.
.
kong_latency_bucket{type=“kong”,service=“google”,le="+Inf"} 2
kong_latency_bucket{type=“request”,service=“google”,le=“00300.0”} 1
kong_latency_bucket{type=“request”,service=“google”,le=“00400.0”} 1
.
.
kong_latency_bucket{type=“request”,service=“google”,le="+Inf"} 2
kong_latency_bucket{type=“upstream”,service=“google”,le=“00300.0”} 2
kong_latency_bucket{type=“upstream”,service=“google”,le=“00400.0”} 2
.
.
kong_latency_bucket{type=“upstream”,service=“google”,le="+Inf"} 2
kong_latency_count{type=“kong”,service=“google”} 2
kong_latency_count{type=“request”,service=“google”} 2
kong_latency_count{type=“upstream”,service=“google”} 2

could you please help me here?

thanks

4

Can you share more details on how you have configured kong and also share the configuration itself?

Please make sure that the plugin is enabled and kong is actively proxying requests when you call the /metrics endpoint.

5

thanks for your reply.

i have checked and updated configuration. now it is working.