kong nginx timers


prometheus query kong_nginx_timers exposes 0 running timers and static number of pending timers all the time. Any explanations? how to test? What query to use in order to alert on too many pending timers?

1 Like

Interested in this too.

We use 2.6 and faced too many pending timers.

Please provide explanation on how to monitor for this using prometheus plugin in later kong versions.

The standard pending timer limit (which you can’t easily change) is 16384. You can set alerts at whatever threshold of that makes sense for you.

If you’re actually hitting it and aren’t sure why, however, you’ll want to try Issues · Kong/kong · GitHub instead–the timer system is internal to the gateway code, not part of the Kubernetes tooling.

Thanks for the reply traines.

Any idea why we timers are static when checking numbers with prometheus?
How can we make timers ‘move’ so we could test everything works?