chore(docs): regenerate man pages (#7971)

man/coredns-trace.7

@@ -1,5 +1,5 @@
 .\" Generated by Mmark Markdown Processer - mmark.miek.nl
-.TH "COREDNS-TRACE" 7 "March 2021" "CoreDNS" "CoreDNS Plugins"
+.TH "COREDNS-TRACE" 7 "March 2026" "CoreDNS" "CoreDNS Plugins"
 
 .SH "NAME"
 .PP
@@ -46,6 +46,9 @@ trace [ENDPOINT\-TYPE] [ENDPOINT] {
     service NAME
     client\_server
     datadog\_analytics\_rate RATE
+    zipkin\_max\_backlog\_size SIZE
+    zipkin\_max\_batch\_size SIZE
+    zipkin\_max\_batch\_interval DURATION
 }
 
 .fi
@@ -64,6 +67,14 @@ Default is \fB\fCcoredns\fR.
 \[la]https://docs.datadoghq.com/tracing/app_analytics\[ra] on the traces sent
 from \fI0\fP to \fI1\fP, \fI1\fP being every trace sent will be analyzed. This is a datadog only feature
 (\fBENDPOINT-TYPE\fP needs to be \fB\fCdatadog\fR)
+.IP \(bu 4
+\fB\fCzipkin_max_backlog_size\fR configures the maximum backlog size for Zipkin HTTP reporter. When batch size reaches this threshold,
+spans from the beginning of the batch will be disposed. Default is 1000 backlog size.
+.IP \(bu 4
+\fB\fCzipkin_max_batch_size\fR configures the maximum batch size for Zipkin HTTP reporter, after which a collect will be triggered. The default batch size is 100 traces.
+.IP \(bu 4
+\fB\fCzipkin_max_batch_interval\fR configures the maximum duration we will buffer traces before emitting them to the collector using Zipkin HTTP reporter.
+The default batch interval is 1 second.
 
 
 .SH "ZIPKIN"
@@ -150,6 +161,15 @@ trace tracinghost:9411 {
 .fi
 .RE
 
+.SH "METADATA"
+.PP
+The trace plugin will publish the following metadata, if the \fImetadata\fP
+plugin is also enabled:
+
+.IP \(bu 4
+\fB\fCtrace/traceid\fR: identifier of (zipkin/datadog) trace of processed request
+
+
 .SH "SEE ALSO"
 .PP
 See the \fIdebug\fP plugin for more information about debug logging.