BIND 9 returns poor statistics if the bind-dyndb-ldap plugin
The issue was reported on our mailing list.
on one of the authoritative bind instances, i am using views there too, which i might reconsider, i am using the bind-dyndb-ldap plugin to host the zone data in ldap, and when i curl for the json/v1 stats URL, only get back: [brendan@server3 ~]$ curl http://localhost:8053/json/v1/
{ "json-stats-version":"1.7", "boot-time":"2024-02-01T09:01:21.914Z", "config-time":"2024-02-01T09:01:27.425Z", "current-time":"2024-02-06T21:45:33.123Z", "version":"9.18.20" }
even though the statistics are configured. it seems the caching mechanisms are not being used:
++ Cache Statistics ++ [View: internal (Cache: internal)] 0 cache hits 0 cache misses 0 cache hits (from query) 0 cache misses (from query) 0 cache records deleted due to memory exhaustion 0 cache records deleted due to TTL expiration 0 covering nsec returned 0 cache database nodes 0 cache NSEC auxiliary database nodes XX cache database hash buckets XXXXXXXXXX cache tree memory total XXXXX cache tree memory in use 0 cache tree highest memory in use XXXXXXXXX cache heap memory total XXXX cache heap memory in use 0 cache heap highest memory in use [View: _bind (Cache: _bind)] 0 cache hits 0 cache misses 0 cache hits (from query) 0 cache misses (from query) 0 cache records deleted due to memory exhaustion 0 cache records deleted due to TTL expiration 0 covering nsec returned 0 cache database nodes 0 cache NSEC auxiliary database nodes XX cache database hash buckets XXXXX cache tree memory total XXXXX cache tree memory in use 0 cache tree highest memory in use XXXX cache heap memory total XXXX cache heap memory in use 0 cache heap highest memry in use
The reported problem prevents Stork agent from forwarding statistics to Prometheus and Stork server.