<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>trace on CoreDNS: DNS and Service Discovery</title>
    <link>https://coredns.io/tags/trace/</link>
    <description>Recent content in trace on CoreDNS: DNS and Service Discovery</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>CoreDNS - All Rights Reserved</copyright>
    <lastBuildDate>Thu, 08 Sep 2022 18:42:54 +0000</lastBuildDate><atom:link href="https://coredns.io/tags/trace/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>trace</title>
      <link>https://coredns.io/plugins/trace/</link>
      <pubDate>Thu, 08 Sep 2022 18:42:54 +0000</pubDate>
      
      <guid>https://coredns.io/plugins/trace/</guid>
      <description>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.</description>
    </item>
    
  </channel>
</rss>
