mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-09-26 16:11:53 +02:00
Code Issues Packages Projects Releases Wiki Activity
coredns/plugin/trace
History
Bob d8d2c16905
plugin/trace - Use compatible tag name for datadog (#4408) 
Traces are currently working properly with datadog with the exception of having the ability to facet the tags

![image](https://user-images.githubusercontent.com/5513509/105051238-dddbbd00-5a6e-11eb-8fb2-071b3b1fa8cc.png)

In order to get valuable graph in dashboard the tag on the metrics need to be faceted by datadog.
This PR update the tags with facetable path.
While keeping backward compatibility with existing path for zipkin.

Graph like:
![image](https://user-images.githubusercontent.com/5513509/93375960-339e1f80-f859-11ea-81f0-a1074c375630.png)
![image](https://user-images.githubusercontent.com/5513509/93375997-4153a500-f859-11ea-9f8d-63d45217c681.png)
![image](https://user-images.githubusercontent.com/5513509/93376064-5597a200-f859-11ea-823a-6768f59e3497.png)
![image](https://user-images.githubusercontent.com/5513509/93376405-d6ef3480-f859-11ea-8d6f-58dda247cc86.png)
![image](https://user-images.githubusercontent.com/5513509/93376518-069e3c80-f85a-11ea-9a7e-0426a3817439.png)

Signed-off-by: bob <bob.bouteillier@datadoghq.com>
2021-01-28 16:38:24 +01:00
..
log_test.go
Clean up tests logging (#1979)
2018-07-19 16:23:06 +01:00
README.md
Update README.md (#4331)
2020-12-11 21:07:25 +00:00
setup_test.go
plugin/trace: Fix zipkin json_v2 (#4180)
2020-11-10 19:03:14 +00:00
setup.go
auto go fmt
2020-11-11 12:30:39 +00:00
trace_test.go
plugin/trace - Use compatible tag name for datadog (#4408)
2021-01-28 16:38:24 +01:00
trace.go
plugin/trace - Use compatible tag name for datadog (#4408)
2021-01-28 16:38:24 +01:00

README.md

trace

Name

trace - enables OpenTracing-based tracing of DNS requests as they go through the plugin chain.

Description

With trace you enable OpenTracing of how a request flows through CoreDNS. Enable the debug plugin to get logs from the trace plugin.

Syntax

The simplest form is just:

trace [ENDPOINT-TYPE] [ENDPOINT]
  • ENDPOINT-TYPE is the type of tracing destination. Currently only zipkin and datadog are supported. Defaults to zipkin.
  • ENDPOINT is the tracing destination, and defaults to localhost:9411. For Zipkin, if ENDPOINT does not begin with http, then it will be transformed to http://ENDPOINT/api/v1/spans.

With this form, all queries will be traced.

Additional features can be enabled with this syntax:

trace [ENDPOINT-TYPE] [ENDPOINT] {
    every AMOUNT
    service NAME
    client_server
    datadog_analytics_rate RATE
}
  • every AMOUNT will only trace one query of each AMOUNT queries. For example, to trace 1 in every 100 queries, use AMOUNT of 100. The default is 1.
  • service NAME allows you to specify the service name reported to the tracing server. Default is coredns.
  • client_server will enable the ClientServerSameSpan OpenTracing feature.
  • datadog_analytics_rate RATE will enable trace analytics on the traces sent from 0 to 1, 1 being every trace sent will be analyzed. This is a datadog only feature (ENDPOINT-TYPE needs to be datadog)

Zipkin

You can run Zipkin on a Docker host like this:

docker run -d -p 9411:9411 openzipkin/zipkin

Note the zipkin provider does not support the v1 API since coredns 1.7.1.

Examples

Use an alternative Zipkin address:

trace tracinghost:9253

or

. {
    trace zipkin tracinghost:9253
}

If for some reason you are using an API reverse proxy or something and need to remap the standard Zipkin URL you can do something like:

trace http://tracinghost:9411/zipkin/api/v1/spans

Using DataDog:

trace datadog localhost:8126

Trace one query every 10000 queries, rename the service, and enable same span:

trace tracinghost:9411 {
	every 10000
	service dnsproxy
	client_server
}

See Also

See the debug plugin for more information about debug logging.