19 Srp
2019
19 Srp
'19
19:14
Hiya,
trying to get our knot dns server (FreeBSD pkg, 2.8.1) to export
prometheus statistics.
I found https://github.com/ghedo/knot_exporter, which looks promising
(and I found that knot-resolver has this all built in, but this doesn't
help me :-/ ).
So, I've installed the required python modules, and when I start
the knot_exporter (with the right paths and everything) it complains
to me:
$ /tmp/knot_exporter --web-listen-port 4041 --knot-library-path ...
Traceback (most recent call last):
File "/tmp/knot_exporter", line 489, in <module>
args.knot_socket_timeout,
File "/usr/local/lib/python3.6/site-packages/prometheus_client/registry.py",
line 24, in register
names = self._get_names(collector)
File "/usr/local/lib/python3.6/site-packages/prometheus_client/registry.py",
line 64, in _get_names
for metric in desc_func():
File "/tmp/knot_exporter", line 434, in collect
for zone, zone_data in zone_stats["zone"].items():
KeyError: 'zone'
so, I read the manual, and it says that this should be sufficient:
template:
- id: default
storage: /usr/local/etc/dnsmgmt/data/CA/knot
disable-any: true
acl: [ acl_transfer, acl_notify ]
global-module: mod-stats
with or without
mod-stats:
- id: default
request-protocol: on
server-operation: on
edns-presence: on
flag-presence: on
response-code: on
reply-nodata: on
query-type: on
... but it does not seem to make a difference.
So - if one of you has a working knot-server knot.conf that exports data
to prometheus, can you share it?
thanks,
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
20 Srp
20 Srp
14:25
Hi Gert,
I don't know knot_exporter, but I guess you have to configure the module per zone:
template:
- id: default
module: mod-stats
However, such a setup consumes more memory in the case of many zones.
Daniel
On 8/19/19 7:14 PM, Gert Doering wrote:
Hiya,
trying to get our knot dns server (FreeBSD pkg, 2.8.1) to export
prometheus statistics.
I found https://github.com/ghedo/knot_exporter, which looks promising
(and I found that knot-resolver has this all built in, but this doesn't
help me :-/ ).
So, I've installed the required python modules, and when I start
the knot_exporter (with the right paths and everything) it complains
to me:
$ /tmp/knot_exporter --web-listen-port 4041 --knot-library-path ...
Traceback (most recent call last):
File "/tmp/knot_exporter", line 489, in <module>
args.knot_socket_timeout,
File "/usr/local/lib/python3.6/site-packages/prometheus_client/registry.py",
line 24, in register
names = self._get_names(collector)
File "/usr/local/lib/python3.6/site-packages/prometheus_client/registry.py",
line 64, in _get_names
for metric in desc_func():
File "/tmp/knot_exporter", line 434, in collect
for zone, zone_data in zone_stats["zone"].items():
KeyError: 'zone'
so, I read the manual, and it says that this should be sufficient:
template:
- id: default
storage: /usr/local/etc/dnsmgmt/data/CA/knot
disable-any: true
acl: [ acl_transfer, acl_notify ]
global-module: mod-stats
with or without
mod-stats:
- id: default
request-protocol: on
server-operation: on
edns-presence: on
flag-presence: on
response-code: on
reply-nodata: on
query-type: on
... but it does not seem to make a difference.
So - if one of you has a working knot-server knot.conf that exports data
to prometheus, can you share it?
thanks,
Gert Doering
-- NetMaster
21:36
Hi,
On Tue, Aug 20, 2019 at 02:25:41PM +0200, Daniel Salzman wrote:
I don't know knot_exporter, but I guess you have
to configure the module per zone:
template:
- id: default
module: mod-stats
However, such a setup consumes more memory in the case of many zones.
I do have
> template:
> - id: default
> storage: /usr/local/etc/dnsmgmt/data/CA/knot
> disable-any: true
> acl: [ acl_transfer, acl_notify ]
> global-module: mod-stats
so what's the difference between "global-module" and "module"
here?
(The examples for the stats module show "global-modul", which is why
I have it)
But it does the trick! Now the exporter is willing to start, and give
me data :-)
Alas, it's a bit on the heavy side, with 7 metrics for ~9600 zone - and
no global metrics "for the whole server". Mmmh. Does knot have these
stats, and the exporter just doesn't grab them yet? Or does knot truly
only do stats on a per-zone level?
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
21:52
Hi,
On 2019-08-20 21:36, Gert Doering wrote:
Hi,
On Tue, Aug 20, 2019 at 02:25:41PM +0200, Daniel Salzman wrote:
A global module applies to all zones. It's exactly what you are looking
for.
But it seems knot_exporter expects per zone statistics only. It should
be
easy to extend the exporter. Maybe tomorrow ;-)
Daniel
I don't know knot_exporter, but I guess you
have to configure the
module per zone:
template:
- id: default
module: mod-stats
However, such a setup consumes more memory in the case of many zones.
I do have
> template:
> - id: default
> storage: /usr/local/etc/dnsmgmt/data/CA/knot
> disable-any: true
> acl: [ acl_transfer, acl_notify ]
> global-module: mod-stats
so what's the difference between "global-module" and "module"
here?
(The examples for the stats module show "global-modul", which is why
I have it)
But it does the trick! Now the exporter is willing to start, and give
me data :-)
Alas, it's a bit on the heavy side, with 7 metrics for ~9600 zone - and
no global metrics "for the whole server". Mmmh. Does knot have these
stats, and the exporter just doesn't grab them yet? Or does knot truly
only do stats on a per-zone level?
Gert Doering
-- NetMaster
22:00
Hi,
On Tue, Aug 20, 2019 at 09:52:28PM +0200, daniel.salzman(a)nic.cz wrote:
> so what's the difference between
"global-module" and "module" here?
[..]
A global module applies to all zones. It's exactly what you are looking
for.
Aaah. Nice.
But it seems knot_exporter expects per zone statistics
only. It should
be easy to extend the exporter. Maybe tomorrow ;-)
This sounds promising :-)
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
1722
days inactive
1723
days old
4 comments
3 participants
participants (3)
-
Daniel Salzman -
daniel.salzman＠nic.cz
-
Gert Doering