hashicorp / hashicorp/consul

detailed DNS request metrics

Open
#9,232 0 comments 0 reactions 0 assignees View on GitHub
theme/telemetry type/enhancement
Dominant language
Go
Stars
30.1k
Forks
4.6k
Avg merge
2d 6h
Merged PRs (30d)
43

Description

currently consul (server) is providing metrics for overall incoming DNS requests. It would be nice to have more detailed metrics, that would include counts for each service requests.

This would be extremely valuable in measuring service level metrics, related to response codes of requests from actual service nodes

Metrics could contain: service_id/service name or fqdn, DNS record type, time it took to respond, client IP.

Debug level log does have this information already.
Example from the log
`2020/11/18 22:15:37 [DEBUG] dns: request for name test.service.dc1.discovery.mydomain.com. type AAAA class IN (took 1.46234ms) from client 10.1.0.20:33068 (udp)
2020/11/18 22:15:39 [DEBUG] dns: request for name test.service.dc1.discovery.mydomain.com. type A class IN (took 1.635725ms) from client 10.1.0.20:36349 (udp)
2020/11/18 22:15:40 [DEBUG] dns: request for name test.service.dc1.discovery.mydomain.com. type A class IN (took 4.91848ms) from client 10.1.0.201:33464 (tcp)
2020/11/18 22:15:41 [DEBUG] dns: request for name test.service.dc1.discovery.mydomain.com. type A class IN (took 9.772059ms) from client 10.1.0.20:35081 (udp)
2020/11/18 22:15:41 [DEBUG] dns: request for name test.service.dc1.discovery.mydomain.com. type A class IN (took 8.44425ms) from client 10.1.0.20:33540 (tcp)`

at the moment we are using consul v1.3.1

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.