From 0a16644ba87b9506829484a34617823c8459fc00 Mon Sep 17 00:00:00 2001 From: Igor Velikorossov Date: Tue, 1 Dec 2020 09:12:13 +1100 Subject: [PATCH] Update host-tracing.md (#45389) --- docs/design/features/host-tracing.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/design/features/host-tracing.md b/docs/design/features/host-tracing.md index 78f4b3c..10ed802 100644 --- a/docs/design/features/host-tracing.md +++ b/docs/design/features/host-tracing.md @@ -9,10 +9,10 @@ Currently (as of .NET Core 2.1) the host tracing is only written to the `stderr` For .NET Core 3 the proposal is to keep the existing behavior as described above and add two additional ways to capture the tracing: * Redirect the trace to a file (always appends) - this would be done by setting `COREHOST_TRACE=1` and also `COREHOST_TRACEFILE=` in the environment for the process. * Add a knob to control trace verbosity `COREHOST_TRACE_VERBOSITY`. If unset tracing will be exhaustive. When set in the range 1-4 the tracing verbosity will increase with an increase in the value of `COREHOST_TRACE_VERBOSITY`. - * `COREHOST_TRACE_VERBOSITY=1 will show errors - * `COREHOST_TRACE_VERBOSITY=2 will show errors and warnings - * `COREHOST_TRACE_VERBOSITY=3 will show errors, warnings, and info - * `COREHOST_TRACE_VERBOSITY=4 will show errors, warnings, info, and verbose. + * `COREHOST_TRACE_VERBOSITY=1` will show errors + * `COREHOST_TRACE_VERBOSITY=2` will show errors and warnings + * `COREHOST_TRACE_VERBOSITY=3` will show errors, warnings, and info + * `COREHOST_TRACE_VERBOSITY=4` will show errors, warnings, info, and verbose. * For custom host support a way to capture the trace output in code. This will be done by adding `*_set_trace_listener` functions to `hostfxr` and `hostpolicy` which would let the custom host intercept all tracing. This is directly related to #4455. -- 2.7.4