From 2950fbe9b2c68a119466f43118c93b234ad7dd8e Mon Sep 17 00:00:00 2001 From: Genevieve Warren <24882762+gewarren@users.noreply.github.com> Date: Tue, 19 Apr 2022 14:25:01 -0700 Subject: [PATCH] fix build suggestions --- .../core/diagnostics/eventsource-collect-and-view-traces.md | 6 +++--- docs/core/diagnostics/eventsource-instrumentation.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core/diagnostics/eventsource-collect-and-view-traces.md b/docs/core/diagnostics/eventsource-collect-and-view-traces.md index 232a255c02337..cd22ece047432 100644 --- a/docs/core/diagnostics/eventsource-collect-and-view-traces.md +++ b/docs/core/diagnostics/eventsource-collect-and-view-traces.md @@ -85,13 +85,13 @@ keyword-based filtering, and "Demo" does no keyword or level filtering. ## Visual Studio -The [Visual Studio profiler](https://docs.microsoft.com/visualstudio/profiling) supports both collecting and viewing traces. It also can view traces +The [Visual Studio profiler](/visualstudio/profiling) supports both collecting and viewing traces. It also can view traces that have been collected in advance by other tools, such as [dotnet-trace](./dotnet-trace.md). ### Collect a trace Most of Visual Studio's profiling tools use predefined sets of events that serve a particular purpose, such as analyzing CPU usage or allocations. To -collect a trace with customized events, you'll use the [Events Viewer](https://docs.microsoft.com/visualstudio/profiling/events-viewer) tool. +collect a trace with customized events, you'll use the [Events Viewer](/visualstudio/profiling/events-viewer) tool. 1. To open the Performance Profiler in Visual Studio, select **Alt**+**F2**. @@ -177,7 +177,7 @@ of that type in the table on the right. ### Learn more -To learn more about using PerfView, see the [PerfView video tutorials](https://docs.microsoft.com/shows/PerfView-Tutorial/). +To learn more about using PerfView, see the [PerfView video tutorials](/shows/PerfView-Tutorial/). ## dotnet-trace diff --git a/docs/core/diagnostics/eventsource-instrumentation.md b/docs/core/diagnostics/eventsource-instrumentation.md index 65e691d020e53..05cb5d9983ea0 100644 --- a/docs/core/diagnostics/eventsource-instrumentation.md +++ b/docs/core/diagnostics/eventsource-instrumentation.md @@ -187,7 +187,7 @@ enabled. ### Setting OpCodes and Tasks -ETW has concepts of [Tasks and OpCodes](https://docs.microsoft.com/windows/win32/wes/defining-tasks-and-opcodes) +ETW has concepts of [Tasks and OpCodes](/windows/win32/wes/defining-tasks-and-opcodes) which are further mechanisms for tagging and filtering events. You can associate events with specific tasks and opcodes using the and properties. Here's an example: