Add files via upload

Adding references to logpoints and snapshot debugger

Author: Sagar-S-S

docs/debugger/using-tracepoints.md

@@ -98,7 +98,7 @@ The behavior of the  **When changed**  option is different for different program
 - For native code, the debugger doesn't consider the first evaluation of the condition to be a change, so doesn't hit the tracepoint on the first evaluation.
 - For managed code, the debugger hits the tracepoint on the first evaluation after **When changed**  is selected.
 
-For a more comprehensive look at valid expressions you can use while setting conditions, see [Expressions in the debugger](expressions-in-the-debugger.md)
+For a more comprehensive look at valid expressions you can use while setting conditions, see [Expressions in the debugger](expressions-in-the-debugger.md).
 
 ### Hit count
 A hit count condition allows you to send output only after the line of code where the tracepoint is set has executed a specified number of times.
@@ -130,10 +130,13 @@ Sometimes when you inspect a property or attribute of an object, its value can c
 
 The way that expressions are evaluated in the **Action** message box may be different than the language you are currently using for development. For example, to output a string you do not need to wrap a message in quotes even if you normally would while using `Debug.WriteLine()` or `console.log()`. Also, the curly brace syntax (`{ }`) to output expressions may also be different than the convention for outputting values in your development language. (However, the contents within the curly braces (`{ }`) should still be written using your development language’s syntax).
 
+If you are trying to debug a live aplication and looking for a similar feature, check out our logpoint feature in the snapshot debugger. The snapshot debugger is a tool used to investigate issues in production applications. Logpoints also allow you to send message to the Output Window without having to modify source code and will not impact your running application. For more information, see [Debug live Azure application](../debugger/debug-live-azure-applications.md).
+
 ## See also
 
 - [What is debugging?](../debugger/what-is-debugging.md)
 - [Write better C# code using Visual Studio](../debugger/write-better-code-with-visual-studio.md)
 - [First look at debugging](../debugger/debugger-feature-tour.md)
 - [Expressions in the debugger](expressions-in-the-debugger.md)
 - [Use breakpoints](../debugger/using-breakpoints.md)
+- [Debug live Azure application](../debugger/debug-live-azure-applications.md)