You can test like this: *curl -sS localhost:9119/metrics | grep bind_up* # HELP bind_up Was the Bind instance query successful? # TYPE bind_up gauge bind_up 1
If bind_up is 0 then it's failing to communicate to bind over the statistics channel. On Friday, 21 January 2022 at 08:31:47 UTC Brian Candler wrote: > On Friday, 21 January 2022 at 04:56:36 UTC [email protected] wrote: > >> - should bind exporter and bind server on a same server? Can we install >> bind exporter on a different server? >> > > https://github.com/prometheus-community/bind_exporter#troubleshooting > > "It's *recommended* to run the bind_exporter next to BIND, so it's only > necessary to open a port locally." [my emphasis] > But you can query the stats from a remote exporter if you need to. > > >> if we install on a different server, which parameters should be >> specified? Whether the following parameter is enough? >> --bind.stats-url=http://XXX:8053/ >> - we encounter an issue that we cannot get any metrics which are required >> to be collected by bind exporter, any critical ACL we haven't set? >> > > Did you change this in your bind config? > > statistics-channels { inet 127.0.0.1 port 8053 allow { 127.0.0.1; }; > }; > > You'll need to bind to a different interface than 127.0.0.1 (maybe 0.0.0.0 > for "all interfaces"), and you'll need to allow the source IP of your > exporter. > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/8f210697-1ccd-46d3-b696-efb168186b7dn%40googlegroups.com.
