You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: trace-dispatcher/doc/trace-dispatcher.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -306,15 +306,15 @@ The usual form to provide a configuration is via a configuration file, wich can
306
306
can be given based on a namespace are:`severity`, `detail`, `backends`and`limiter`.
307
307
308
308
Backends can be a combination of `Forwarder`, `EKGBackend`, `PrometheusSimple [suffix|nosuffix] [bindhost] <port>` and
309
-
one of `Stdout MachineFormat`, `Stdout HumanFormatColoured` and `Stdout HumanFormatUncoloured`.
309
+
one of `Stdout MachineFormat`, `Stdout HumanFormatColoured` and `Stdout HumanFormatUncoloured`.
310
310
311
311
The connection for the `Forwarder` backend is provided on the application command line. It is a socket path over which applications like `cardano-node` connect with `cardano-tracer`. `--tracer-socket-path-connect /path/to/forward.sock` sets
312
312
the backends's role to `Initiator`, whereas `--tracer-socket-path-accept /path/to/forward.sock` sets it to `Responder`. Except for debugging purposes, the former should be chosen: the application takes the `Initiator` role, and `cardano-tracer` is
313
-
in the `Responder` role, which means setting its network `tag` to `AcceptAt` in its config (see there).
313
+
in the `Responder` role, which means setting its network `tag` to `AcceptAt` in its config (see there).
314
314
315
315
The `PrometheusSimple` backend provides Prometheus metrics _directly from the process_, without forwarding. It always applies to all tracers globally, and should only be configured once.
316
316
Providing an available port number in the connection string is mandatory; this will bind to localhost only by default. By specifying a bind host, the metrics can be queried remotely, e.g. over IPv4 by
317
-
binding to `0.0.0.0`, or IPv6 by binding to `::`. Metrics will be available under the URL `/metrics`.
317
+
binding to `0.0.0.0`, or IPv6 by binding to `::`. Metrics will be available under the URL `/metrics`.
318
318
The `nosuffix` modifier removes suffixes like `_int` from metrics names, making them more similar to those in the old system; `suffix` is the implicit default and can be omitted.
319
319
320
320
*CAUTION*: Generally allowing remote queries of Prometheus metrics is risky and should only be done in an environment you control.
@@ -691,6 +691,11 @@ The consistency checks cover the following aspects:
691
691
692
692
- Any namespace in the configuration must be found by a hierarchical lookup in `all namespaces`.
693
693
694
+
If the checker encounters any problems it emits a `TracerConsistencyWarnings` message through the
695
+
`Cardano.Logging.TraceDispatcherMessage` type. The message is routed via the `Reflection` namespace
696
+
and carries `Warninig` severity so that misconfigured namespaces are surfaced prominently in both the
697
+
logs and forwarded tracing output.
698
+
694
699
## Trace Backends Overview
695
700
696
701
As mentioned earlier, trace backends serve as the final destinations for all traces once they have undergone trace interpretation, resulting in metrics and messages. The system defines three trace backends:
0 commit comments