From 020ec8da45bc9c877bf10c5d44d10fccee9ca460 Mon Sep 17 00:00:00 2001 From: Mario Hewardt Date: Thu, 9 May 2019 08:55:06 -0700 Subject: [PATCH] Update intermittent_memory_spike.md --- documentation/tutorial/intermittent_memory_spike.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/tutorial/intermittent_memory_spike.md b/documentation/tutorial/intermittent_memory_spike.md index b3b1692c6..bbb55a942 100644 --- a/documentation/tutorial/intermittent_memory_spike.md +++ b/documentation/tutorial/intermittent_memory_spike.md @@ -53,8 +53,8 @@ Events that are written to the EventPipe can come from multiple sources (or prov #### Writing the tool... We have two requirements in order to implemented a tool that will create a dump file based on memory consumption: -+Being able to read dotnet memory counter to know when it breaches the specified threshold -+Generate the actual core dump +* Being able to read dotnet memory counter to know when it breaches the specified threshold +* Generate the actual core dump Let's start with the first requirement, reading dotnet counters. As explained earlier, we can use the EventPipe mechanism to read counters from the runtime. In this case, the provider that writes counter events is System.Runtime. Below is the code that sets up the System.Runtime provider for use in our tool: -- 2.34.1