Skip to content

Conversation

mikelle-rogers
Copy link
Member

This document explains how to instrument code and consume data with DiagnosticSource/DiagnosticListener

This document explains how to instrument code and consume data with DiagnosticSource/DiagnosticListener
Copy link
Member

@noahfalk noahfalk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would combine this page and the getting started page into a single PR so they can be reviewed together.

## Consuming Data with DiagnosticListener

Up until now, this guide has focused on how to instrument code to generate logging
information. In this section we focus on subscribing and decoding of that information.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title of this article was "Instrument Code ..." so the portion above here seemed on-topic, but below it no longer matches the title. I'd suggest changing the title to something broader (or moving the content about listening to a separate page is an alternative)

#### Subscribing to DiagnosticListeners

A `DiagnosticListener` implements the `IObservable<KeyValuePair<string, object>>` interface, so you can
call `Subscribe()` on it as well. We show how to fill out the previous example:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the style recommendation for docs is to use 2nd or 3rd person rather than 1st person.

@mikelle-rogers
Copy link
Member Author

Closing pull request because I combined all diagnosticsource documentation into one pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants